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

Goes meaningfully beyond annotations by disclosing business rules: the day must have room (5) and the account must stay 7 days from its other comments. These are non-obvious constraints an agent cannot infer from idempotentHint/destructiveHint. Does not state permission/auth requirements or what happens on constraint violation.

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?

One dense but well-structured sentence covering all four operations and two constraints; no filler. Slightly packed but every clause carries operational weight.

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 5-param mutation with no output schema and sparse schema descriptions, the description covers the required operations, the implicit field interactions, and the scheduling constraints. Lacks failure-mode detail and which fields are required for each status, but otherwise complete.

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 only 20% (only 'date' documented). Description compensates by explaining 'date' accepts 'next' semantically ('the next good day'), 'status' drives which other params apply (skip_reason for skipped), and implying 'comment' holds the new wording. Still leaves 'id' and skip_reason formats implicit.

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 precise set of operations (edit wording, reschedule, mark posted/skipped, revert to pending) on a specific resource (queued IG comment). Clearly distinct from siblings like queue_ig_comment, ig_comment_queue, and shearquery_instagram_reply_comment.

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?

Explicitly scopes the audience (ShearQuery team) and enumerates each status transition with its precondition ('after someone posted it on Instagram'). Does not name a sibling tool as an alternative, but the operation set is unambiguous for a management/CRUD tool.

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