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

Discloses API limitations (no GET by id, no cancel/delete) and bulk execution support. This adds value beyond annotations which already mark it as read-only and idempotent. No contradiction with annotations.

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?

Highly concise, with key information front-loaded. Every sentence adds value without 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?

Lacks description of output format/fields, which is important given no output schema. Covers filtering and limitations well, but does not describe pagination response or error handling.

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?

Adds meaning to most parameters: date format for data_inicio/data_fim, pagination limits, and the role of cliente_ids for batching. However, the 'account' parameter is not described, and there is no explanation of return value structure.

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 'Lista contratos' with specific filtering criteria (date interval, pagination, client ID, text search) and bulk support. It implicitly distinguishes from sibling tools like get_contract (single contract) and delete_contract.

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?

Provides explicit context on date parameter defaults (wide window if omitted) and pagination max size (50). Mentions bulk cliente_ids for batched execution. Does not explicitly contrast with get_contract or other list tools, but the sibling names are distinct enough.

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