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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating a safe read operation. The description adds pagination and date-range context, but doesn't disclose behavior like empty results or rate limits. It adds moderate value beyond 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 with two short sentences, front-loading the main purpose. Every word adds value, and no extraneous information is present.

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 output schema, and 0% coverage, the description is too sparse. It fails to explain what 'ofertas publicas' means in this context or the role of the 'account' parameter. The agent may need to infer details that are not provided.

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 has 0% parameter description coverage, so the description must compensate. It partially explains 'page' for pagination and implies 'dataInicio' and 'dataFim' define the range, but doesn't clarify 'account' parameter. Given the low coverage, the explanation is insufficient.

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 the tool lists public offerings (IPOs/subscriptions) for an investor within a date range. The verb 'list' and resource 'ofertas publicas' are specific, and pagination is mentioned. While it distinguishes from siblings by focusing on offerings, it doesn't explicitly differentiate from similar list tools.

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 implies usage with a date range ('num intervalo') and pagination ('Paginado por page'), but provides no explicit guidance on when to use this tool versus alternatives. No when-not or alternative tool references are given.

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