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

Annotations already communicate readOnly, idempotent, and non-destructive behavior. The description only adds the HTTP method and endpoint path; it does not disclose pagination behavior, auth requirements, filtering semantics, or what endpoints or states are covered.

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 brief sentence: 'Orçamentos: Listar (GET /api/orcamentos).' It has no filler and front-loads the main operation, but the brevity comes at the expense of valuable context.

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?

With two optional parameters, 0% schema coverage, and no output schema, the description leaves important invocation details unstated. The agent knows this is a GET list endpoint but does not know what the query/account parameters mean, what the response contains, or which sibling endpoint is more appropriate in a given context.

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%, and the description does not explain the 'query' or 'account' parameters at all. The agent is left without any indication of what these parameters mean, how they affect the result, or what formats are expected.

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 says 'Orçamentos: Listar' and includes the exact endpoint 'GET /api/orcamentos', so the action and resource are clear. It does not go further to describe scope, filtering, or what items are returned, so it is clear but not fully informative.

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?

There is no guidance about when to use this tool versus sibling tools like gestaoclick_orcamentos_get, gestaoclick_orcamentos_create, or gestaoclick_atributos_orcamentos_list. No prerequisites, exclusions, or alternatives are mentioned beyond the implied list operation.

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