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

Goes well past the annotations with details they cannot express: one report per network per entry, re-sending mutates the existing report, a 100-per-24h-per-network cap, how the report is counted (anon_worked/anon_failed) and that it weighs less in ranking, no note field, no IP stored, and operator test traffic excluded. Idempotency is correctly implied and consistent with idempotentHint=true, and the write/anonymous nature matches readOnlyHint=false.

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?

Two dense sentences that front-load the action and the worked true/false values before moving to limits and counting rules. Every clause carries information, though the compressed punctuation-heavy style makes it slightly harder to scan than it could be.

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 two-parameter, non-destructive write with no output schema, it covers everything an agent needs: anonymity, idempotency behavior, rate limits, ranking weight, exclusions, and the sibling to use instead. Nothing material is left unstated.

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 percent, so both parameters (id, worked) are already fully documented in the schema, including the 'k' prefix convention. The description adds only the scope constraint that a report is per network per entry, with no further syntax or format detail beyond the schema.

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 opens with a specific verb and resource ('Report ... whether a shared fix worked for you') and immediately gives the value domain (worked true or false). It explicitly separates itself from the keyed sibling by naming confirm_knowledge, so an agent can distinguish the two without inspecting either 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?

Clear routing: use this when you have no key, use confirm_knowledge when you do, and an explicit exclusion ('Not for open questions'). It does not spell out the trigger condition (after actually applying/testing the fix) in so many words, so the boundary is slightly inferred rather than fully stated.

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