check_twilio_number

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

The annotations already disclose that this is a non-read-only, non-destructive, non-idempotent, open-world operation. The description adds useful context that it repairs/re-syncs webhook configuration, but it does not explain side effects, what existing configuration may be overwritten, or what the result looks like. With annotations covering the safety profile, this is adequate but not rich.

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?

The description is front-loaded, compact, and every sentence adds useful information. It covers purpose, usage context, exclusion, and payload expectations without unnecessary repetition.

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 one-parameter mutation tool with annotations and no output schema, the description gives enough information to invoke it correctly: purpose, timing, exclusion, and expected payload fields. It is only slightly incomplete because it does not describe return behavior or side effects in more detail.

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 description coverage is 100%, so the baseline is 3. The description goes further by explaining that the payload is the full request body for /utils/twilio/check-number and typically includes phoneNumber or phoneNumberSid, which adds practical guidance beyond the schema's generic object definition.

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 clearly states a specific action: repair / re-sync the Twilio SMS/voice webhook configuration for a number. It also distinguishes the tool from WhatsApp Cloud API health checks. However, it does not distinguish this from the sibling sync_sms_twilio_number tool, which could otherwise seem related.

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?

The description gives a clear usage context: use it when call/SMS routing breaks. It also includes an exclusion by stating it does not check WhatsApp Cloud API health. It does not, however, mention alternatives such as sync_sms_twilio_number, import_twilio_number, or release_twilio_number.

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