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

No annotations are provided, so the description carries the full burden. It does disclose a non-obvious behavioral trait: reports must agree and be backed by an agent/API key or confirmed runs before a bounty opens. It omits attribution of the report, auth requirements, and rate limits.

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 sentences, front-loaded with the action and scoped to the payload before explaining the bounty consequence. Little waste, though the bounty sentence is somewhat tangential to invocation.

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-required-param mutation tool with no annotations and no output schema, the description covers purpose and consequence but leaves auth mechanics, what a successful submission returns, and the semantics of source_id and the kind values unexplained.

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 only 33%, so the description should compensate, but it merely repeats 'kind and note' without explaining source_id or the meaning of each kind value (broken vs stale vs incorrect vs other). The enum is self-documenting in the schema, but the uncovered parameters get no help.

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+resource: reporting a maintained source as broken or stale, naming the two payload fields (kind, note). It is distinguishable from the sibling request_source, which presumably asks for a new source rather than flagging an existing one, though that contrast is not made explicit.

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?

The description describes the downstream effect (a repair bounty opens) rather than when to choose this tool over alternatives like request_source or maintenance. Usage is implied by the phrase 'appears broken or stale' but no explicit when/when-not guidance or prerequisites are given.

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