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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-scope questions are answered structurally. The description adds one genuinely useful behavior (off-brand Traveller article links are filtered), but says nothing about pagination, result limits, or freshness beyond the word 'current'.

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?

One compact sentence that front-loads the action and resource, then the parameter source, then the filtering caveat. Every clause earns its place with no filler.

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. For a single required parameter read tool, the description covers purpose, parameter origin, and one filtering quirk; only edge cases like empty sections or invalid slugs are unaddressed.

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 single 'section' parameter has no schema-level documentation, so the description carries the burden. It does so by defining the parameter as a slug obtained from brisbanetimes_sections, which meaningfully compensates for the schema gap, though it gives no format example.

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 (Fetch), a specific resource (current story cards), and a precise scope (one Brisbane Times section or populated topic page), which cleanly separates it from sibling brisbanetimes_article, brisbanetimes_author, brisbanetimes_news, and brisbanetimes_sections.

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 tells the agent the value must be a slug drawn from brisbanetimes_sections, which is real routing guidance toward the sibling that supplies the parameter. It does not state when to prefer brisbanetimes_news over this tool, so it falls short of full when/when-not coverage.

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