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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that only public profiles are reachable and that the response bundles recent article cards, but says nothing about auth, rate limits, or missing-profile behavior.

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 tight sentence that front-loads the verb and resource and tucks the URL format and return contents in without padding. Nothing wasted.

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 single-parameter, read-only tool with an output schema, the description covers the essential retrieval contract (URL form, public scope, article cards). The output schema handles return structure, so the remaining gap is minor.

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?

With one parameter at 0% schema coverage, the description must compensate: it specifies that the url must be a canonical /by/<name>-<id> value, which is meaningful format guidance the bare 'string' schema lacks. It stops short of examples or validation rules.

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 uses a specific verb ('Fetch') and resource ('Brisbane Times journalist profile'), and pins down the exact URL form (/by/<name>-<id>). It clearly reads as a profile-fetch tool distinct from article/headlines/news/sections siblings, though it doesn't explicitly name those alternatives.

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 via 'canonical /by/<name>-<id> URL' and the 'public' qualifier, signalling that a valid canonical profile URL is required. However, it never states when to prefer this over brisbanetimes_article or other author/article tools, leaving routing to inference.

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