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. The description adds some behavioral context by listing profile contents, but doesn't discuss auth needs, rate limits, or profile-visibility constraints. With annotations carrying the safety burden, a 3 is appropriate.

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, front-loaded with the tool's purpose before the input instruction, with no wasted text. Every clause carries information.

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 need not be re-explained, and annotations cover the safety profile; the description nonetheless summarizes contents. The parameters are fully documented. Only the lack of inter-tool routing guidance keeps it from a 5.

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%, so the schema documents both url and slug. The description goes beyond the schema by explaining where to source the value ('from an article byline or canonical profile URL'), which adds real meaning to the slug parameter. It also implicitly frames slug and url as alternatives.

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 (The National author's public topic profile), and enumerates the contents returned (name, optional author image, recent story cards). This clearly distinguishes it from siblings like national_article, national_headlines, national_news, and national_sections.

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?

It tells the agent how to supply the input ('a slug from an article byline or canonical profile URL'), which is practical, but gives no explicit when-to-use-vs-alternative guidance and names no sibling tool. Usage is implied rather than framed against alternatives.

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