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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds one genuinely useful behavioral detail — that only the 'first page' of stories is returned, implying a paginated/truncated result — but says nothing about auth, rate limits, or what happens with an invalid url/slug.

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 efficient sentence that front-loads the entity being fetched and lists the return fields without filler. Nothing is wasted, though it spends words enumerating fields an output schema already covers.

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?

Because an output schema exists, the field enumeration is largely redundant, and the description leaves the two input parameters completely unspecified while giving no usage context. It is adequate to recognize the tool but incomplete for invoking it correctly.

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 description coverage is 0% and the description never mentions the url or slug parameters, so the agent has no guidance on which identifier to supply, their formats, or whether one is preferred. With two undocumented parameters this is a real gap.

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 names a specific resource ('one RNZ reporter's public profile') and enumerates the exact fields returned, so the agent knows this fetches a single author entity. It distinguishes itself from siblings like rnz_article/rnz_news by virtue of being an author-profile tool, though it does not explicitly contrast with them.

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?

There is no when-to-use guidance, no indication of when to prefer this over rnz_article or rnz_news, and no hint about the relationship between the url and slug inputs. The agent must infer usage entirely from the name.

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