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

Annotations already declare write semantics and openWorldHint, but the description adds real context beyond them: support may follow up, only the reported issue is transmitted (no conversation history or PII), Fiveable resolves content and reporter identity, and matching requestId retries are idempotent. It repeats the idempotentHint already in annotations, so it falls short of fully additive disclosure, but the data-handling and follow-up behavior are genuinely new information.

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?

Four short sentences, front-loaded with purpose and approval requirement, and each sentence carries distinct information (gating, scope of payload, resolution ownership, idempotency). Slightly dense/packed, but no filler.

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 destructive-capable write tool with an output schema present, the description covers the confirmation gate, payload scope, privacy handling, and retry semantics, which is most of what an agent needs. It does not say what happens on failure or how support follow-up is surfaced, but the output schema can carry that.

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 60%, so the description must carry some weight, and it does: it constrains 'description' to the issue only (excluding transcripts and unrelated personal notes) and clarifies 'confirmReport' as gated on an explicit student request. It also notes idempotency keyed on requestId. contentType and contentId semantics are left to the schema.

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 and resource ('Submits a caller-requested content issue to Fiveable support') with a clear destination. No sibling tool in the list does anything comparable, so an agent can route to it unambiguously. The purpose is stated in the first clause without requiring the title.

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 gives a hard precondition ('Requires explicit confirmReport approval') and scopes intake to caller-requested issues, which implies when the tool may be used. However, it does not contrast with any alternative action (e.g., answering the student directly or searching content first), so usage guidance is implied rather than explicit.

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