add

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

The description indicates a return value ('devolve o resultado') but does not explicitly state that the operation is side-effect free or pure. Since no annotations are present, the description carries the full burden and could be slightly more explicit.

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 concise sentence with no unnecessary words. It directly conveys the operation and result.

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 addition tool, the description is complete: it states the inputs (two numbers), the operation (sum), and the output (result). No additional context is needed.

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 schema provides names and types for the parameters, and the description mentions 'dois números', which loosely covers both. However, it does not add specific meaning beyond the schema, so it meets the baseline but does not exceed it.

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 'Soma dois números e devolve o resultado' clearly states the tool's function (addition) with a specific verb and resource. Even without siblings, the purpose is unambiguous.

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 explicit usage guidance is provided, but the simple arithmetic nature makes the intended use obvious. There are no alternative tools to contrast with, so the absence of 'when to use' is acceptable but not fully informative.

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