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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds the bulk execution trait ('accepts ids for batched execution'), which is beyond the annotation set. However, it does not disclose potential error handling, pagination, or response format, but given the annotation coverage, this is acceptable. No contradiction with 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 extremely concise, consisting of two short sentences. It front-loads the primary purpose and adds a single relevant note about bulk support. There is no fluff, and every sentence contributes. However, it might be too minimal, but for conciseness it earns a high score.

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 4 parameters, no schema descriptions, and no output schema, the description must provide substantial context. It only explains the basic GET action and bulk support, leaving 'query' and 'account' unexplained, and no indication of return values or error scenarios. The tool is not adequately described for an agent to use it confidently without additional 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%, so the description must explain parameters. It only mentions 'ids' for bulk support, but does not explain 'id', 'query', or 'account'. The description does not compensate for the lack of schema descriptions, leaving most parameters ambiguous.

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 it is a read operation for suppliers ('Fornecedores: Visualizar (GET /api/fornecedores/{id})') and mentions bulk support via 'ids'. This distinguishes it from the sibling list, create, update, and delete tools. However, it could be more explicit about what data is returned, but the core 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?

There is no explicit guidance on when to use this tool versus the list tool or how to handle bulk vs single retrieval. The mention of bulk support hints at a use case, but it does not explain when to prefer this over alternatives or provide any exclusions (e.g., 'use list to retrieve all suppliers'). The description fails to give clear usage context.

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