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

Adds substantial context beyond the annotations: it states feedback is untrusted observation with no effect on work, proof, payment, safety, authority, standards or code, discloses rate limiting and keyless/no-signer auth, and gives an explicit secrets-exclusion rule. That is rich behavioral disclosure for a write-shaped call. It stops short of a 5 because it never says what happens to the submission afterward (review, triage, dedupe) despite idempotentHint=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?

Front-loaded with the core instruction, which is good, but the cost/signer fact is stated twice ("Free and keyless" near the start and "Cost and signer: free and keyless (rate-limited), nothing to sign" at the end). That duplication costs space in an otherwise tight definition.

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 return values need no explanation, and the description covers cost, auth, privacy limits, and the non-effects of submitting. For a 9-parameter open-world write tool the remaining gap is the post-submission lifecycle and how evidenceRefs should be chosen, but nothing an agent needs in order to call it 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% and every property including the targetKind enum is already documented, so the schema carries the load. The prose maps loosely onto attemptedIntent/observedResult/expectedResult, but adds no format, limit, or evidenceRefs guidance beyond what the schema states. Baseline 3 applies.

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?

Names a specific verb and resource: record what you attempted, what happened, and what you expected, and the scope sentence ("a tool, endpoint, page or capability is missing, confusing, blocked or appears broken") makes the domain unmistakable. It does not explicitly distinguish itself from submit_request, which plausibly overlaps on 'missing capability', so sibling differentiation is left to inference.

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?

"Use this when a tool, endpoint, page or capability is missing, confusing, blocked or appears broken" is a concrete trigger condition with five enumerated failure modes. There is no explicit when-not or named alternative (e.g. submit_request for new capabilities), so it stops short of full routing guidance.

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