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/mutability profile is covered structurally. The description adds one genuinely useful behavioral fact — that self-reports cannot assign verified evidence status — but says nothing about auth requirements, the effect of visibility, the meaning of the record_kind/outcome_state enums, or how idempotency is applied. Modest added value over 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?

Two short sentences, front-loaded with the core action and zero filler, which is structurally clean. But for a 16-parameter write tool with nested objects and a conditional schema, this brevity crosses into under-specification rather than efficient conciseness.

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?

Given 16 parameters, 9 required, 0% schema description coverage, nested objects, an allOf conditional, and no output schema, the description is drastically incomplete. It never addresses what the caller must supply, what the required idempotency_key is for, or what 'owner-approved' and 'verified evidence status' concretely require.

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% across 16 parameters (9 required) with nested objects, so the schema documents no parameter semantics itself and the description must compensate. The description explains no parameter at all — nothing on goal, result, actions, conditions, sources, idempotency_key, outcome_state, share_approved, or private_note. The full burden is unmet.

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: 'Submit an ... outcome or failure.' An agent knows this is a write that records an outcome. However, it does not differentiate itself from siblings like get_outcome, search_outcomes, or create_request, and the qualifiers 'owner-approved' and 'minimal' are undefined jargon that leave the exact artifact ambiguous.

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?

'Owner-approved' implies a prerequisite condition, which is a faint usage cue. Beyond that there is no when-to-use guidance, no mention of alternatives such as search_outcomes or get_outcome, and no indication of when to prefer this over related write tools. Guidance is largely absent.

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