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

Annotations only tell the agent this is a non-read-only, non-idempotent, open-world, non-destructive call; the description adds the materially important consequence that approving publishes publicly and that edits (caption/platforms) must happen before approval. It omits permission/auth requirements and confirmation that repeated calls with the same proposalId fail, so it stops short of full disclosure.

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, front-loaded with the verb pair and the irreversible public-publish consequence immediately after. Every clause carries decision-relevant information with 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 7-parameter, nested-object mutation tool with no output schema and only 57% schema coverage, the description covers the main approve/reject flows and the public-publish side effect well. It is still silent on the scheduledFor and reasonNote overrides and on what a successful decision returns, which leaves minor gaps for an agent handling approval-with-edits.

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 57%, and the description adds useful intent for caption (override before approving) and platforms (add/change before approving) plus the learning-loop role of the reject reason. It never explains scheduledFor (publish-time override) or reasonNote, leaving two parameters entirely 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 pair (approve/reject) and a specific resource (pending Autopilot post proposal), and names clipember_list_autopilot_proposals as the source, which distinguishes it from the other 29 siblings. An agent can tell immediately this is the decision endpoint for proposals rather than a creation or scheduling tool.

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?

Gives clear context for both branches: approving schedules a public publish, rejecting removes from the queue. It does not, however, say when an agent should reject versus escalate, or when to use this instead of clipember_create_scheduled_post / clipember_cancel_scheduled_post for the same content, so the alternative-routing is left implicit.

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