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

Annotations already declare readOnlyHint=true, so description need not repeat. Description adds useful behavioral context: stories are 'active and developing' and have 'chapters ordered by chapter index.' No contradiction or missing destructive 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?

Three sentences: purpose, structure, usage guidance. Front-loaded, no unnecessary words. Each sentence 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?

The tool is simple (one optional parameter, output schema exists) and the description covers purpose and usage context well. Could mention if there are any limitations like pagination, but not critical for this straightforward list tool.

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 only parameter (locale) is optional with enum and default, but the description does not mention it or explain its effect. With 0% schema description coverage, the description should compensate; it fails to add any value for parameter understanding.

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 clearly states it lists active and developing breaking-news stories with chapters, distinguishing it from sibling tools like list_live_moments (which lists individual moments) and get_live_story (which retrieves a specific story). The verb 'list' and resource are explicit.

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 says when to use: 'when you want to surface the narrative arc... rather than each moment in isolation.' Also provides guidance on next steps: 'Pass a returned story id to get_live_moment for the current snapshot.' This helps the agent choose between tools and chain them.

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