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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. With no output schema, the description usefully enumerates the fields the agent will receive (name, has_audio, duration_ms, source, script_text) and flags the domain constraint that only drops with audio can be used by voicemail_drops_drop. It omits ordering, pagination, and volume behavior, keeping this below a 5.

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 sentence, verb-front-loaded, with every element carrying information and no filler. The parenthetical aside about has_audio slightly interrupts the field enumeration but adds genuine value.

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 no-parameter list tool with no output schema, the description supplies the essential return field set, which is the main gap it needed to fill. However it says nothing about result volume, ordering, or whether results are paginated, which an agent calling a list endpoint would benefit from knowing.

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?

The tool takes zero parameters, so the baseline is 4. The field list in the description refers to returned data rather than inputs, which is appropriate for a parameterless lister.

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 (voicemail drops), and is easily distinguished from the sibling mutations voicemail_drops_create/delete/drop/update. It does not explicitly say it returns all drops in the account or how it relates to the other voicemail tools, so it stops just short of a 5.

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?

There is no when-to-use guidance, no mention of prerequisites, and no references to alternative tools such as voicemail_drops_drop despite that tool being directly related ('only drops with audio can be dropped'). The agent must infer the role of this tool from its name alone.

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