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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, and an output schema documents the return shape. The description adds only that the payload comprises profile, headshot, biography and recent articles, which largely overlaps the purpose statement – useful but not deep behavioral context (no pagination/limit on 'recent articles').

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?

Two sentences, zero filler, with the resource and input front-loaded before the disambiguation clause. Every sentence 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?

For a single-parameter, read-only profile fetch with annotations and a published output schema, nothing an agent needs to invoke it correctly is missing. Return values are documented by the output schema, so the description need not restate them.

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 description coverage is 100% and the schema states 'Canonical The Indian Express author URL'. The description repeats the same hint ('canonical author `url`') without adding format, example, or accepted-variant guidance. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

Specific verb (Fetch) plus resource (Indian Express author's public profile, headshot, biography, recent articles) and the exact input ('from canonical author `url`'). The second sentence names sibling tools and the content type each covers, so an agent can distinguish this from indianexpress_article/headlines/news without opening a schema.

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 the agent to the three alternatives and the condition that selects each ('one story', 'section headlines', 'general feed'). It doesn't state an explicit when-not for this tool, but the alternatives plus the stated scope make the choice unambiguous.

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