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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds real value: it discloses pagination semantics (nextCursor present only when more results remain), how to resume, and graceful degradation when the tracker database is unavailable. That is behavior an agent could not infer from the structured fields.

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?

Front-loads what the catalogue is before pagination mechanics; every sentence carries information. The cursor instruction is slightly verbose for something the schema also states, keeping it just under top marks.

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?

With an output schema present, return-value detail is unnecessary, and the description still covers content shape, next-step routing, pagination and failure mode. Nothing an agent needs to invoke or continue 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?

Schema coverage is 100%, so limit, theme and cursor are already documented including enum-like theme values. The description restates the cursor continuation contract but adds no format or constraint detail beyond the schema, which is the expected baseline case.

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 resource (MMA statistical series catalogue grouped by theme) with what each entry contains (latest figure, year-on-year change) and explicitly separates it from the retrieval sibling get_tracker_series. An agent can distinguish it from list_indicators or search tools without opening the schema.

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 onward: 'Open one with get_tracker_series', which names the alternative and the condition that selects it. It does not cover when to prefer other listing tools (e.g. list_indicators), so it stops short of full when/when-not guidance.

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