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

Annotations (readOnlyHint: false, destructiveHint: false) indicate a mutating but non-destructive action. Description adds value by disclosing cost ($0.0083/SMS) and return values (message SID and delivery status), which go beyond annotations. No contradiction detected.

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?

Description is extremely concise: one sentence plus pricing, with no superfluous words. It uses an emoji for visual cue and front-loads the action. Every sentence earns its place.

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?

Despite the tool being simple, the description covers purpose, prerequisite (Twilio number), cost, and return values. Since an output schema exists, return values are further detailed elsewhere. The description is complete for an agent to understand what the tool does and what to expect.

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 baseline is 3. Description does not add new information about parameters beyond what the schema already provides (E.164 format for to/from, max length for body). Therefore, it meets the baseline but does not exceed it.

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?

Description clearly states 'Send SMS message to any phone number worldwide' with a specific verb and resource. It distinguishes from sibling SMS tools by specifying 'Twilio' and including pricing, making the tool's purpose unambiguous.

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?

Description explicitly states a prerequisite: 'Requires a Twilio phone number as sender.' It gives clear context about sending worldwide and pricing. While it does not explicitly mention alternatives or when not to use, the context is sufficient for an agent to decide when to invoke this tool.

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