Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds the polling semantics (status may not be final on first call), which the annotations cannot express. It does not describe terminal statuses, error states, or what 'structured content analysis' contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the polling purpose and appends the retrieval payload. No wasted words and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the return-value burden, and 'structured content analysis' is left unelaborated — an agent cannot tell what fields to expect or whether a pending status is a normal first response. For a status-polling tool, a note on retry/terminal states would close the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

One parameter with 0% schema description coverage, so the schema supplies only type/format/pattern and no human meaning. The description's 'one source's' ties the id to a content source, which is marginal added value; it says nothing about where the sourceId comes from (create_content_source or list_content_sources).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair (poll / retrieve) and the exact resource: one source's analysis status plus its structured content analysis. An agent can distinguish it from list_content_sources (plural) and from the create/delete/reanalyze siblings. It does not explicitly differentiate itself from get_content_job or get_content_piece, which is the only gap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'poll' implies an iterative use pattern (call repeatedly until analysis completes), which is real, if implicit, guidance. There is no explicit when-to-use/when-not statement and no named alternative such as reanalyze_content_source or list_content_sources for discovery.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.