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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and reach profile is covered. The description adds the content scope (profile, contact links, recent articles), but no behavioral detail like pagination or auth is disclosed; an output schema exists, so return values need not be explained here.

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, no filler. The purpose and its scope are front-loaded, and the sibling routing follows immediately, so an agent gets both facts in one pass.

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?

Given an output schema (so returns need not be described) and annotations covering safety, the description supplies everything left: what is fetched, the input form, and how to choose among the mediaite siblings. Nothing an agent needs to call this correctly is missing.

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 both url and slug are documented in the schema. The description's phrase 'from a canonical author URL' merely echoes the url param's documented form ('Canonical mediaite.com/author/<slug>/') without adding new meaning, so the baseline of 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 ('a Mediaite author's public profile, contact links, and recent articles'), and names the siblings it is not (mediaite_article, mediaite_news). An agent can distinguish it from those siblings without opening any 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 away with 'Use mediaite_article for a story's content or mediaite_news for the general feed', which is clear when-not guidance. The when-to condition (fetching by canonical author URL) is only implied by the first sentence rather than stated as a directive.

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