twilio_list_calls

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The phrase 'outbound and inbound' adds a little scope context (no direction preselection), but nothing is said about authentication requirements, pagination, or result volume for an open-world remote API call.

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?

A single clean sentence, front-loaded with the verb and resource, with zero filler. It is efficient but so short that it avoids rather than earns its scope.

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 6-parameter tool requiring credentials, with low schema coverage and no output schema, the description should say what the auth parameters are, which filters exist, and what a listing returns. None of that is present, so an agent would need to infer usage entirely from the 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 description coverage is only 17% — just the status value list — so the description must compensate and does not. It never explains that account_sid/auth_token are required, what 'from'/'to' filter on, or how page_size behaves, leaving five of six parameters undocumented anywhere.

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 (list) and resource (calls) with explicit scope: 'outbound and inbound calls on a Twilio account.' An agent can distinguish it from twilio_list_messages or twilio_make_call by resource, but the description does not name any sibling to reinforce the boundary.

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?

No when-to-use guidance, no mention of alternatives like twilio_make_call or twilio_get_message, and no note that credentials must be supplied to read a specific account's calls. The intent is only implied by the verb 'list.'

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