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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false), so the safety bar is met structurally. The description adds genuinely useful context beyond that: submissions land in a review queue, nothing is published until reviewed, and fields must not contain personal data. It stops short of describing auth/account requirements or what happens after review.

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 tight sentences with no filler. The core action is front-loaded, the three content types follow, and the constraints (review gating, no personal data) land last where they read as guardrails.

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 7-parameter write tool with no output schema, the description covers the important behavioral facts an agent needs: what it submits, that it goes to review, and the PII prohibition. It leaves out whether authentication/registration is needed and whether a confirmation or identifier is returned, which are minor since no output schema exists.

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 71%, with `agent` and `kind` carrying no schema description at all, so the description does useful work by defining what a use case, lesson, and correction are. However, it adds nothing about the undocumented `agent` parameter or how `playbook` is required for corrections/lessons, leaving those gaps 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?

The description gives a specific verb ('sends') plus the resource and enumerates the three accepted content types (use case, lesson, correction), mapping them to the `kind` enum. It implicitly separates itself from the sibling submit_playbook by framing corrections as changes to existing playbooks, but never names that sibling, so the differentiation is inferred rather than stated.

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?

'a job done with an agent that has no playbook yet' hints at when a use case is appropriate, but there is no explicit when-to-use/when-not guidance and no routing to submit_playbook for a brand-new playbook. Usage is implied rather than specified.

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