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

Annotations already declare readOnly/idempotent/non-destructive and closed-world; the description adds the genuinely useful fact that this is static knowledge that does NOT hit the API, so the agent knows the result is canonical documentation rather than live account state. It also flags sensitive content covered (credential masking, read-only/system-managed fields), which helps the agent trust and apply the output.

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?

Purpose and the static/no-API caveat are front-loaded, then the covered topics are enumerated in one dense sentence. The enumeration is long but each item helps the agent judge relevance; minor trimming of the topic list would tighten it further.

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?

There is no output schema, so the description carries the burden of conveying what comes back — and it does, by itemizing the content areas (storage locations, safe patch fields, masking, coexistence, page mapping, Twilio separation). Combined with annotations covering safety and the schema covering section selection, an agent has everything needed to call it correctly.

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% and the single enum parameter's description already explains what "whatsapp", "metaPages" and "sms" contain. The description's topic list roughly mirrors those sections without adding selection guidance beyond the schema, so baseline 3 applies.

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 ("Return static Convocore channel-integration schema guidance") and scopes it to concrete channels (WhatsApp, Messenger, Instagram, SMS). It clearly separates itself from action-oriented siblings like update_whatsapp_number_settings or get_whatsapp_ai_rules by being documentation, not an API 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?

"Use this before configuring or explaining WhatsApp, Facebook Messenger, Instagram, or SMS routing" gives an explicit trigger condition, and the Twilio SMS warning steers the agent away from send_sms/sync_sms_twilio_number for WhatsApp Cloud API numbers. It stops short of naming the exact sibling doc tools (e.g. get_ui_engine_spec) an agent might confuse it with, or stating when this tool is not needed.

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