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 what the profile contains, which is useful, but says nothing about pagination, auth, or how 'latest stories' is bounded. Some added value over the annotations, but thin.

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 compact sentence that front-loads the resource and lists the returned fields without waste. Nothing redundant, though it is arguably too terse given the undocumented parameters.

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 needn't be spelled out, and annotations cover the read-only profile. However, with 0% schema coverage and no parameter guidance in the description, an agent lacks enough information to invoke the tool correctly (which of url/slug to supply). Adequate but with a clear gap.

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 0% with two parameters (url, slug) and no required flag, and the description never mentions either parameter, so it does not compensate for the coverage gap. An agent cannot tell from the description whether url or slug is expected, mutually exclusive, or optional.

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 resource (one National Post author's public profile) and enumerates the returned content (name, bio, story count, latest stories), which distinguishes it from nationalpost_article and nationalpost_news. It is clear but relies on the publisher prefix to differentiate it from the many other *_author siblings rather than explaining any distinction itself.

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?

No guidance on when to use this tool versus nationalpost_article or nationalpost_headlines, and no hint about identifying an author. Nothing indicates the conditions under which this is the right call.

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