get_contacts

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

With no annotations provided, the description carries the full burden. It states the tool retrieves all contacts, implying a read-only operation, but does not explicitly confirm it has no side effects or describe the output format. The description is adequate but minimally transparent.

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 only two sentences, both front-loaded with the primary purpose and usage hint. Every word serves a purpose, with zero redundancy or unnecessary detail.

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?

Given a single parameter, no output schema, and a clear context from sibling tools, the description is mostly complete. It explains what the tool does and a prerequisite, but lacks details about the return format or any limitations (e.g., no pagination). It meets the needs for a simple retrieval tool.

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 schema already describes the list_key parameter with 100% coverage. The description adds value by specifying that this key is obtained via list_agendas, which provides context beyond the schema definition.

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 uses the verb 'Obtiene' (gets) and specifically identifies the resource as 'todos los contactos de una agenda específica' (all contacts of a specific agenda). This clearly distinguishes it from sibling tools like add_contact, delete_contact, etc., which perform other operations.

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 explicitly instructs to use list_agendas first to obtain the list_key, providing clear prerequisite guidance. This helps the agent understand the correct invocation order and use case for this tool.

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