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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful behavioral context beyond annotations: the 15-minute capture cadence and the authentication requirement via X-API-Key or Authorization: Bearer. It does not describe pagination or exhaustive return behavior, but it adds enough context for a read-only time-series tool.

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?

The description is front-loaded with the core purpose, then usage guidance, then an auth note. Every sentence contributes necessary information, and there is no redundant restatement of the tool name or schema. It is appropriately sized for a two-parameter read tool.

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?

Given the simple schema, full parameter description coverage, annotations, and lack of an output schema, the description provides enough detail to call the tool correctly. It covers purpose, usage sequencing, data cadence, and auth requirements. No critical operational detail for this tool appears to be 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?

Schema description coverage is 100%, so both parameters are already documented in the schema. The description reinforces that the tool operates on one narrative but does not add syntax, constraints, or examples beyond what the schema provides. Baseline 3 is appropriate because the schema carries the parameter semantics.

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 states a specific resource and scope: a time series for ONE narrative, including 15-minute captures of phase, velocity, article and source counts. It also distinguishes this tool from the sibling muhabbit_narratives by framing this as a follow-up for lifecycle evolution. An agent can tell what the tool returns and when it differs from the related list tool.

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?

It explicitly says to use this after muhabbit_narratives to see how a story's lifecycle evolved, including the question it answers ('accelerating or rolling over'). This gives both the prerequisite sibling call and the intended analytical use case. The guidance is clear enough that an agent does not need to infer when to choose this over muhabbit_narratives.

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