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

With annotations already declaring readOnlyHint=false, idempotentHint=true and destructiveHint=false, the bar is lower, and the description adds real value: it discloses the aggregated threshold effect (multiple distinct flags hide the trace pending review). It does not cover auth requirements or what a single flag alone does, but the key side-effect is surfaced.

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 action and effect, with no filler. The bilingual repetition adds length without new information, which slightly reduces efficiency but keeps it scannable.

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 single-parameter mutation with no output schema and annotations carrying the safety profile, the description supplies the missing piece: what flagging ultimately accomplishes. Nothing critical for correct invocation appears absent.

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?

There is a single parameter whose schema description coverage is 100%, so the schema already defines 'id' as the trace Id. The description adds no format, syntax, or constraint detail beyond the schema, so the baseline of 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?

States a specific verb (flags) plus resource (a trace) and enumerates the possible flag reasons (spam, prompt-injection, off-topic), so an agent knows exactly what the call does. It does not differentiate itself from siblings, but the sibling verbs are clearly distinct operations.

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 conveys the consequence ('Enough distinct flags hide it pending review'), which implies context of use, but it never states when to prefer this over siblings like ack_trace or leave_trace, nor any preconditions. Usage is inferable rather than explicit.

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