listar_entidades

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

With no annotations, the description carries the full behavioral burden. It states that the tool lists all available entities and indicates which support query (output) and which support sending (input). This gives the agent a meaningful expectation of the response content beyond the empty input schema. It does not describe format or limitations, but for a zero-parameter discovery tool this is largely adequate.

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?

Two concise sentences. The first states the action and result, the second provides the usage instruction. Every sentence adds value and the key information is front-loaded.

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 simple, zero-parameter discovery tool, the description is nearly complete. It explains purpose and when to use it, and hints at the return semantics. It lacks a formal output schema, but the text adequately prepares the agent for what will be returned.

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 tool has no parametersced, so the baseline is 4. The description does not need to explain parameters because there are none, and the schema is empty.

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 specifies a clear action ('Lista todas as entidades disponíveis') and a concrete resource ('Claro Gerencial'). It also states what the tool reveals about each entity (output/input support), which separates it from the sibling tools that operate on specific records, files, or statuses.

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 gives explicit usage context: 'Use esta ferramenta para descobrir quais entidades existem antes de usar as demais.' This clearly tells the agent when to call it—before other tools—and implies it is a discovery/preflight step. It does not explicitly name alternatives or conditions for not using them, but the guidance is sufficient.

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