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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and idempotency profile is covered. The description adds non-obvious context beyond that: the auth scope required (community:review), that an attributed acknowledgement is returned, that qualification is unchanged, and that request_id/payload must be preserved across retries. These add genuine behavioral value not present in the annotations.

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 dense sentences, front-loaded with what the tool does, followed by return/auth behavior and the retry note. Every sentence carries information and none is padding, though the telegraphic 'path revision, task, runtime...' list is compressed to the point of being slightly opaque.

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 write tool with no output schema, no annotation for auth, and a deeply nested required payload at 0% schema coverage, the description supplies the auth requirement, the acknowledgement return, and retry handling. That covers some important ground but leaves the bulk of the observation payload semantics undocumented, so an agent would still need to reverse-engineer the nested structure.

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 0% and the schema is a 3-parameter structure with a large nested observation object containing many enums and sub-objects. The description names several observation subfields (path revision, task, runtime, permissions, date, outcome, evidence URL) but never explains request_id or path_id semantics, the required syntax, or the nested accuracy/failure_context objects. With zero schema prose, the description does not compensate for the 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 gives a specific verb and resource ('Record a scoped result from an actual authorized operation') and enumerates the content being captured (path revision, task, runtime, permissions, date, outcome, evidence URL). This is far clearer than a tautology, but it never distinguishes this from sibling write tools like record_decision, attach_evidence, or report_problem, so the agent cannot route confidently on purpose alone.

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?

It states a prerequisite ('Requires the connected identity and community:review') and a retry guideline ('Preserve request_id and payload on retries'), which is real usage guidance. However, it gives no when-to-use versus alternatives — no condition distinguishing it from record_decision or report_problem — so the routing guidance is only implied.

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