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

Annotations declare readOnlyHint=false and destructiveHint=true, yet the description reads purely as a reporting/status read and gives no clue why the operation is destructive or what state it affects. It also adds no information about auth, rate limits, or side effects, so the surprising destructive classification is left unexplained. It does not explicitly contradict the annotations, but the framing is misleading for a mutating 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?

It is one long, clause-chained sentence dense with undefined jargon ('S1', 'decided flag', 'declared bounds') and no front-loaded statement of action. Length is moderate but the structure obscures rather than conveys meaning.

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 the field enumeration in the description is largely redundant with structured data, while the genuinely needed context — what the tool does, when to call it, what it mutates, and how to supply series_id — is absent. For a destructive, open-world tool this is materially incomplete.

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 single parameter series_id has 0% schema description coverage, and the description never mentions it — no format, no reference to list_series or register_series for obtaining a valid id. With an undocumented required parameter, the description fails to compensate for the schema gap.

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 never states a verb or the operation's intent; it enumerates output fields ('published share, published aggregate, remaining slots, required remainder, decided flag, model estimate') rather than saying what the tool does. Nothing distinguishes it from siblings like decided_strikes or required_remainder, which appear to return overlapping data.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the eleven sibling tools. The leading token 'FREE' hints at a tier distinction but is never explained or tied to a selection condition.

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