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 the content scope (profile, bio, recent items), but that largely restates what the output schema will carry, and it says nothing about auth requirements, whether the URL must come from another Salon tool, or pagination of the article list.

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, both front-loaded: the capability first, the sibling routing second. No filler, no repetition of the schema.

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 no explanation, and annotations cover the read-only/open-world profile. What is missing is where to obtain the canonical author URL (presumably from salon_article or salon_headlines results), which is the only practical gap for an agent calling this tool.

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% with a single required parameter, so the schema already documents `url`. The description's one contribution is the word 'canonical', hinting the URL must be a normalized writer URL rather than any Salon link, but it adds no format or acquisition detail. Baseline 3 is appropriate.

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 a precise resource ('Salon writer's public profile, biography, and recent article items') keyed on a canonical author URL. It also disambiguates itself from three named siblings, so an agent can select it 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?

Explicit routing: salon_article for one story, salon_headlines for section headlines, salon_news for the general feed, salon_sections to browse sections. This is a clear when-to-use-this-vs-alternatives map, not implied guidance.

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