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

Annotations already declare readOnlyHint=false and destructiveHint=true, but the description adds real information beyond them: merge semantics (only sent fields change), that auto_reply sends messages with no human review, and the Instagram 24-hour/writer-first constraints. It stops short of saying what happens to a config when fields are unset to null, which is the main remaining risk with destructiveHint=true.

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 create-or-update merge behavior, followed by side-effect warnings and platform limits in descending order of importance. No filler or restated field documentation.

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 mutation tool with no output schema, the description covers purpose, merge behavior, side effects, auth scope, and platform limits — enough to call it correctly. What it lacks is what the call returns or how to verify the resulting config, which is a minor gap given the absence of an output schema.

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 100%, so the baseline is 3; the description earns above that by explaining merge semantics, which is parameter behavior the schema does not convey — it tells the agent that omitted params are preserved rather than cleared. It does not map individual params like enabled vs auto_reply, but the schema already covers those interdependencies.

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 (create or update) and resource (responder config), plus the crucial upsert detail that the first call creates the config. It does not distinguish itself from nearby siblings such as configure_autopilot, get_responder, or set_conversation_responder, so an agent must infer which of these to call.

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 useful context — requires write scope, and Instagram's 24-hour reply window and writer-first rule — which implicitly tells the agent when this tool is useful. However, it never says when not to use it or names an alternative such as set_conversation_responder for per-conversation overrides, leaving selection between siblings to inference.

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