list_providers

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

Annotations already indicate read-only (readOnlyHint=true). The description adds transparency by detailing the search scope (multiple fields) and the summary flag's effect on returned fields. It does not contradict annotations and provides useful behavioral context beyond structured fields.

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 two sentences in Spanish, front-loaded with the main action, and contains no unnecessary words. Every sentence provides valuable information.

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 the tool's simplicity and the presence of an output schema (not shown), the description covers the search behavior and summary option adequately. It could mention pagination explicitly, but the schema provides defaults. Overall, it is fairly complete for a list 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?

With schema description coverage at 0%, the description compensates by explaining the 'q' parameter (searches in specific fields) and the 'summary' parameter (returns a reduced set of fields). The 'page' and 'page_size' parameters are not explained but are standard pagination with defaults; the description adds meaningful value for the non-obvious parameters.

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 it lists providers ("Lista proveedores") and explains the search parameter and summary behavior. However, it does not explicitly differentiate from sibling list tools like list_customers, so it is clear but not explicitly distinguishing.

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 through the search and summary options but provides no explicit guidance on when to use this tool versus alternatives like get_provider or other list tools. No when-to-use or when-not-to-use advice is given.

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