zyta_expedientes_honorarios_create

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

With no annotations, the description carries full burden for behavioral disclosure. It only states it registers fees and provides the HTTP method. It does not mention side effects (e.g., does it create a record? Is it safe or destructive?), required permissions, idempotency, or any other behavioral traits.

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 very short (one sentence + endpoint hint), but it is underspecified rather than concise. It omits critical information, failing the requirement that every sentence earns its place.

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 complexity (13 parameters, no output schema, no annotations), the description is grossly incomplete. It does not explain required vs optional fields, relationships, return values, or any operational context needed to use the tool effectively.

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 only 8% (one parameter has a description). The tool description adds no parameter-level information. For 13 parameters, the agent gets no help understanding semantics beyond the schema's enum names and types.

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 explicitly says 'Registra honorarios en un expediente' (registers fees in a case), clearly indicating a create operation. Among sibling tools with similar naming (list, update, delete), this distinguishes itself as the creation endpoint. However, it is brief and could be more explicit.

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. There is no mention of prerequisites, when not to use it, or comparison to sibling tools like honorarios_update or honorarios_delete.

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