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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description need not reiterate safety. It adds value by specifying what the response includes ('revision, article context, attribution, sources and canonical_url'), which is not conveyed by annotations or the parameter schema. This enriches the agent's understanding of the operation beyond structured fields.

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?

The description is a single, efficient sentence that front-loads the core action ('Read one section') and then lists supporting details. No wasted words; every phrase contributes to clarifying scope and content.

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?

For a read-only tool with strong annotations and an output schema, the description covers the essential points: what is read, the input context (public article), and the composition of the response. It does not explicitly mention that the IDs come from prior search/list calls, but that is implied by sibling tools and the schema's 'Identifier from a result' phrasing. Overall, it provides sufficient context for an agent to call the tool correctly.

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?

The schema provides descriptions for both parameters ('Identifier from a result'), but these are generic and not very informative. The tool description itself does not explicitly clarify that 'id' refers to the article and 'section_id' to the section, though the noun 'section' in the description hints at it. With 100% schema coverage, the baseline is 3; the description adds minimal supplementary meaning.

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?

The description clearly states a specific verb ('Read'), a precise resource ('one section... of a public article'), and enumerates the data returned ('revision, article context, attribution, sources and canonical_url'). This distinguishes it from the sibling tool read_article, which presumably handles full articles.

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 description implies when to use this tool (when you need a section rather than a whole article) but does not explicitly name alternatives or provide exclusion criteria. There is no direct statement like 'for the full article, use read_article instead,' so the usage context is left to inference.

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