zyta_expedientes_honorarios_list

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

No annotations provided; the description only states HTTP method 'GET', implying read-only but not confirming safety, idempotency, or side effects. Missing details on authentication, rate limits, or pagination behavior beyond schema defaults.

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?

Concise single sentence front-loading the purpose. However, the inclusion of 'GET …/honorarios' is slightly redundant but not detrimental.

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?

Missing output schema, no description of return format, error conditions, or pagination behavior. For a list tool with 4 parameters and no annotations, the description is insufficiently complete.

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 description coverage is 75% (3 of 4 parameters have descriptions). The description adds no additional meaning beyond the schema and does not explain the 'estado' parameter which lacks schema description.

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 specific verb 'Lista' and resource 'honorarios de un expediente', clearly distinguishing from sibling CRUD tools (create, delete, update) and from 'zyta_expedientes_list' which lists expedientes.

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 on when to use vs alternatives, no prerequisites or exclusions mentioned. Usage is only implied by the verb 'lista'.

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