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

Adds genuinely useful behavior beyond the readOnlyHint/openWorldHint annotations: conditional billing (5 credits instead of 1 when AP's edge challenge forces browser rendering) and the constraint that authentication and access controls are not bypassed. These are cost and access facts the annotations cannot convey, though the base 1-credit case and any rate limits are left unstated.

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?

Front-loads the core purpose in the first clause, then layers the cost caveat and alternative routing. Every sentence earns its place, though the routing sentence is dense with four named siblings.

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?

With an output schema present, return values need not be described, and the annotations cover the safety profile; the description fills the remaining gaps (cost, access constraints, sibling routing). For a single-parameter read tool this is close to complete, missing only a precondition note on sourcing the canonical URL.

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 parameter documented as the canonical AP News author URL, so the schema carries the burden. The description reinforces 'canonical author url' but adds no format, example, or derivation guidance beyond that.

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 (AP News author profile) and enumerates the payload: profile, byline, biography, and recent articles. The sibling tools it names (apnews_headlines, apnews_news, apnews_article) make it distinguishable from the other TS news functions without opening a 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 to alternatives: use apnews_headlines/apnews_news to find stories and apnews_article for one story, implying this tool is for author profiles. It gives clear context but never states a negative condition (e.g. when an author profile is NOT the right call) or the precondition that you must already have a canonical author URL.

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