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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds non-obvious behavior: results are 'story cards' (not full articles) and off-brand Traveller links are filtered out, which an agent could not infer from the schema.

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 front-loaded sentence that packs scope, the parameter source, and the filter caveat with no filler. Every clause earns its place.

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?

An output schema exists so return values need not be described, and annotations cover the safety profile. The description supplies scope, parameter source, and filtering behavior; the only gap is the lack of differentiation from the closely named brisbanetimes_news sibling.

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 already enumerates documented slug values, so the baseline is 3. The description adds a cross-tool pointer ('use a slug from brisbanetimes_sections') and notes that both section and topic slugs are accepted, which is not stated in the schema.

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 and resource ('Fetch current story cards') and scopes it to 'one Brisbane Times section or populated topic page'. It differentiates from brisbanetimes_sections by naming it as the slug source, but does not clarify how this differs from the sibling brisbanetimes_news.

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 brisbanetimes_sections to obtain the required slug, which is real usage guidance. It lacks any when-not or alternative-selection guidance (e.g., versus brisbanetimes_news or brisbanetimes_article).

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