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

Annotations already declare readOnlyHint and openWorldHint, covering the safety profile. The description adds the scoping detail that only one page of recent articles is returned, which is useful beyond the annotations, but says nothing about pagination limits, caching, or profile availability for non-staff contributors.

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?

A single well-formed sentence that front-loads the resource and then lists the return contents. No filler, no repetition of the tool name.

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 two-parameter read tool with an output schema and safety annotations, the description is essentially complete: it says what entity is fetched and what fields come back. The only minor gap is that it doesn't flag the 'recent articles' sub-resource as paginated beyond the schema's page parameter.

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 both parameters (url, page) are fully described in the schema. The phrase 'one page of their recent articles' loosely relates to the page parameter but adds no syntax or format detail beyond what the schema already provides, so the 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?

The description clearly states the resource ('One Deadline staff writer or contributor's public profile') and enumerates the fields returned (name, job title, headshot, biography, links, recent articles). It implicitly distinguishes from article/headlines siblings by focusing on a person, though it never names a sibling tool explicitly.

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?

Usage is implied – an agent can infer this is for looking up an author's profile – but there is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives like deadline_article for the writing itself. Minimum viable context only.

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