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

The description's '[write, altera dados]' tag merely restates the annotation readOnlyHint=false and adds no new behavioral context. It does not disclose side effects, authentication needs, or response behavior beyond what annotations already provide.

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 extremely short and front-loaded with the main purpose. However, the '[write, altera dados]' element is redundant given the annotations, so it does not fully earn its place.

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 create operation with an undocumented body and account parameter, the description is critically incomplete. No output schema exists to compensate, and the agent lacks essential information to invoke the tool correctly.

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's two parameters (body and account) have no descriptions and 0% coverage. The description offers no explanation of what values or format these parameters require, leaving the agent unable to construct a valid request body.

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 clearly states the action 'Cadastrar' (create/register) for the resource 'Fornecedores' (suppliers) and gives the HTTP POST endpoint. This specific verb+resource combination distinguishes it from sibling tools like get, list, update, and delete.

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 implies this tool is for creating suppliers via the verb 'Cadastrar' and POST method, but it does not explicitly state when to use it versus alternatives, nor provide exclusions or conditions. Usage guidance is only implicit.

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