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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds the HTTP GET method, which is consistent with those hints, but it does not disclose any further behavioral traits such as filtering, pagination, or response format. It is minimal but not contradictory.

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, front-loaded phrase that clearly identifies the resource and action. It is concise and structured, though it lacks detail; the brevity is acceptable for a simple list operation but borders on under-specification.

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 list tool with no output schema and two undocumented parameters, the description is insufficiently complete. It does not explain the meaning of 'query' or 'account', nor does it indicate what the response contains or any limitations, leaving significant gaps for an agent to use 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 input schema has two parameters (query and account) with no descriptions (0% schema description coverage), and the tool description does not explain their purpose, format, or valid values. The agent receives no information about what these parameters do.

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 'Situações de vendas: Listar' (Sales situations: List) with the HTTP endpoint GET /api/situacoes_vendas, making it unambiguous that this tool lists sales situations. It distinguishes itself from sibling list tools by specifying the unique resource 'situacoes_vendas'.

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 provides no guidance on when to use this tool versus alternatives. It only names the operation without any context about selection criteria, prerequisites, or when the many sibling list tools would be more appropriate.

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