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

Annotations already have readOnlyHint: true. The description adds that the tool does not consume calculator limits and is available when free usage is exhausted, providing useful behavioral context beyond 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?

The description is a single, clear paragraph that front-loads the purpose and includes all essential details without unnecessary repetition or fluff.

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 request tool with no output schema, the description covers what it does, what input is needed, how the response is delivered, and a special condition (no calculator limit consumption). It is complete.

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 0%. The description adds meaning for 'email' and 'escopo' (scope), but does not explain 'nome', 'api_key', or 'empresa'. Partial compensation for the lack of schema descriptions.

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 title and description clearly state this tool is for soliciting a budget for a study/report with ART. It specifies the types of studies (arc flash, short-circuit) and the process (chat, email response). It is distinct from sibling calculation tools.

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?

The description explicitly states what information to provide (email, scope) and how the team responds (via email). It also notes that it does not consume calculator limits and works even when free usage is exhausted, guiding the agent to use it when other tools are unavailable.

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