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

Annotations already declare readOnlyHint: true, idempotentHint: true, destructiveHint: false, covering safety. The description adds that it returns id and label, which is useful. However, it does not mention any other behavioral details, such as whether it requires prior authentication or any rate limits. Since annotations cover the safety profile, a score of 3 is appropriate.

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 that delivers the core information without extra fluff. It is front-loaded and efficient, with no wasted words.

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?

The tool is simple, has read-only annotations, and no output schema. The description states it lists id and label, which is helpful. However, the unexplained 'account' parameter and lack of any usage context (e.g., whether it requires prior authorization) prevent it from being fully complete. It is adequate but with gaps.

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 one optional parameter 'account' (string) with 0% description coverage. The description does not mention or explain this parameter at all. With zero schema coverage, the description fails to compensate, leaving the parameter's purpose 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 verb 'Lista' (lists) and resource 'conexões PagHiper vinculadas a este install' clearly specify what is listed. It distinguishes from sibling 'paghiper_list_bank_accounts' by explicitly naming PagHiper connections and noting linked to this install. Clear and specific.

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 does not explicitly state when to use this tool versus alternatives like 'paghiper_list_bank_accounts'. However, it implies it is for listing PagHiper accounts in this install, which gives context but no exclusions or alternatives.

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