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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this mutates state. The description adds useful gate context (decisions block page approval) but never says whether a recorded disposition is final, overwritable, or what it destroys — the key question for a destructive-hinted call.

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 short sentences, front-loaded with the action, then the workflow constraint, then the dependency. No filler and no repetition of the title.

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?

For a three-parameter mutation tool with no output schema, it covers purpose, gating rule and index source adequately. It stops short of describing the resulting page state or whether re-deciding is permitted, which matters for a destructive-flagged operation.

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 the baseline is 3, but the description adds provenance the schema lacks: claim indexes come from get-hosted-page, telling the agent where to obtain claim_index rather than guessing. It does not elaborate on disposition semantics beyond the enum, which the schema already documents.

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 and resource: record a decision about one flagged claim on a hosted page. It is unambiguously distinct from get-hosted-page (which supplies indexes) and from reject-hosted-page, which the description implicitly contrasts by scoping the action to a single claim.

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?

Gives clear trigger conditions and a workflow prerequisite: every flagged claim must be decided before the page can be approved, and indexes come from get-hosted-page. It does not state whether the disposition can be changed later or how it relates to whole-page rejection, so no explicit when-not guidance.

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