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

Annotations already provide readOnlyHint=true (safe read) and openWorldHint=true (external content). The description adds that the result contains metadata and body paragraphs, which is useful scope information beyond the annotations. It doesn't mention paywalls, rate limits, or content availability, leaving some behavioral gaps.

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?

One sentence, no filler, front-loaded with the resource identity. Every word earns its place.

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?

An output schema exists, so return values needn't be explained. However, for a tool whose only parameter has zero schema description coverage, the description should specify the URL format (e.g., full article URL from indiatoday.in). It is minimally viable but gaps remain.

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 required parameter ('url') with 0% schema description coverage. The description implies the URL identifies an India Today article but adds no format, domain, or syntax details beyond what the parameter name already conveys – a missed opportunity to compensate for zero schema coverage.

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 states a specific verb-less noun phrase identifying the resource: a single article's metadata and body paragraphs from India Today. Sibling tools like indiatoday_headlines, indiatoday_news, and indiatoday_sections make the differentiation clear by name. It doesn't explicitly say 'fetch/retrieve', but the intent is obvious.

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?

Usage is implied – fetch one article by URL – but the description never states when to use this tool vs. indiatoday_headlines or indiatoday_news, nor any prerequisites. The sibling naming convention helps, but no explicit routing guidance is given.

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