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

Annotations already declare readOnlyHint and openWorldHint. The description adds that the profile is public and that it includes recent article cards, which gives useful return-content and access context beyond the annotations, though it does not cover rate limits or pagination.

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 sentence, front-loaded with the action and resource, with no wasted words. It includes only the essential scope details: what is fetched, how it is identified, and what it returns.

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 simple one-parameter read-only fetch with an output schema, the description is complete enough: it names the resource, input format, public nature, and a key return-content element. The output schema can carry the detailed return structure, so no further description is required.

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 the schema describes the url parameter generically as a canonical Brisbane Times journalist URL. The description adds the concrete /by/<name>-<id> path pattern, giving extra semantic guidance for constructing or validating the input.

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 the specific verb 'Fetch' and resource 'Brisbane Times journalist profile', plus the canonical URL shape and that recent article cards are included. This clearly distinguishes it from brisbanetimes_article/news/headlines, which cover articles, news, and lists rather than one journalist profile.

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?

Implies usage by requiring a canonical /by/<name>-<id> URL, but does not explicitly state when to use it over sibling tools such as brisbanetimes_article or brisbanetimes_news. The context is inferable for an agent looking up a journalist profile, but no exclusions or alternatives are named.

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