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

Annotations already cover safety (readOnlyHint, openWorldHint), yet the description adds meaningful behavior: subscriber-only magazine stories return only a public teaser with paywalled=true. This paywall disclosure is genuine value beyond the annotations.

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?

Three tight sentences: what it fetches and from where, the paywall edge case, then the sibling routing. Nothing is redundant and the core purpose is front-loaded.

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?

Output schema exists and annotations carry safety, so the description only needs the paywall caveat and routing — both present. It could note other sibling article options (author/news), but for a single-URL fetch tool this is essentially complete.

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?

Schema coverage is 100% and the single url parameter is fully documented in the schema. The description's 'canonical story url' phrasing reinforces but adds no syntax details beyond the schema, so baseline 3 applies.

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 (Fetch) and resource (India Today article metadata and body paragraphs) scoped to a canonical story URL. The paywall note further clarifies exactly what content comes back, making it clearly distinct from sibling feed tools.

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?

Explicitly routes to indiatoday_headlines for finding stories and indiatoday_sections for browsing topics. It gives clear context but does not state explicit exclusions (e.g., versus indiatoday_news or indiatoday_author).

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