Préstamos otorgados

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

Annotations already declare readOnlyHint=true, and the description's 'consulta' aligns but adds no new behavioral context. It does not mention date range handling, response format, pagination, or any limitations beyond what the schema shows.

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 with no redundant text, but it adds little beyond the tool name and title. It is appropriately short but under-informative.

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 date-filtered query tool, the description is incomplete. It omits the purpose of the date range, does not mention that parameters are optional, and lacks context about the nature of the loan data. Although an output schema exists, the description still fails to give sufficient 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?

The description does not explain the 'desde' and 'hasta' parameters at all, despite schema description coverage being 0%. The parameter names are somewhat self-explanatory as date filters, but the description does not compensate for the lack of schema documentation.

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 queries 'préstamos otorgados' (granted loans) and specifies the domain as 'mercado de valores' (securities market). The verb 'consulta' and resource are specific, and it is distinct from sibling tools, though it does not explicitly differentiate from them.

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?

No guidance is provided on when to use this tool versus alternatives, any prerequisites, or typical use cases. The description only states what it does, not when or why to use it.

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