List the 104 exact Brisbane Times editorial surfaces accepted by brisbanetimes_headlines: 95 article-bearing section pages and nine populated topic hubs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
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 meaningful behavioral context beyond that: the list is an exact, fixed enumeration of 104 items with a stated composition, telling the agent this is a complete static catalog rather than a paginated or dynamic result. No auth/rate-limit detail, hence not a 5.
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 dense sentence that front-loads the verb and resource, then supplies the exact count and breakdown. No filler and no redundancy with the schema or annotations.
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 zero-parameter discovery tool with an output schema, the description only needs to explain what the list represents, which it does precisely (count, composition, and the sibling that consumes it). Nothing an agent needs to call it correctly is missing.
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?
The tool takes zero parameters, so there is nothing for the description to clarify and the baseline is 4. The schema is empty and needs no compensation.
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 ('List') and resource ('Brisbane Times editorial surfaces'), and ties itself to the sibling brisbanetimes_headlines as the consumer. The breakdown (95 article-bearing section pages + nine topic hubs) makes the scope unambiguous and lets an agent distinguish it from brisbanetimes_news or brisbanetimes_article.
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?
The phrase 'accepted by brisbanetimes_headlines' strongly implies when to call this: to discover valid section identifiers before invoking headlines. However, it never explicitly states 'use this to find section values' nor names alternatives (brisbanetimes_news, brisbanetimes_article), leaving the routing slightly to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
