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

With no annotations, the description carries the full behavioral burden. It discloses the sort order ('mais recentes primeiro'), which is useful, but does not state that the operation is read-only, describe pagination behavior, or clarify authentication or response shape.

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 concise sentence that front-loads the core action and resource, with the ordering detail included. No filler or redundancy.

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 simple 3-parameter listing tool with no output schema, the description covers the basic action and ordering. However, with no annotations and no output schema, it could do more to explain pagination expectations, return shape, and how searching interacts with listing.

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 schema already documents page, search, and pageSize. The description only loosely reflects the search parameter through 'busca' and adds no syntax, format, or behavioral detail beyond the schema baseline.

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 states the specific verb and resource: lists or searches account transcriptions, with a defined ordering ('mais recentes primeiro'). It is distinguishable from get_transcription by implying a collection rather than a single item, but it does not explicitly name sibling tools or clarify 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?

Usage is implied by 'Lista ou busca', but there is no explicit guidance on when to use this tool versus get_transcription, nor when to use the search parameter versus listing all transcriptions. No exclusions or prerequisites are given.

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