roiq_update_card

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

No annotations provided; description implies mutation (actualiza) but does not disclose idempotency, side effects, permissions, or error handling. The behavioral burden is entirely on the description, which is insufficient.

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?

Single sentence, front-loads the purpose with no wasted words. However, could benefit from brief structure (e.g., listing fields or usage note).

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?

Despite 5 parameters (1 required), no output schema, and nested objects, the description is too minimal. It does not explain partial updates, validation, or behavior when code is not found.

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 coverage is 0% on parameters; description lists field names but adds minimal semantics. For example, 'props' allows arbitrary key-value pairs but no format or constraints are explained.

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 verb 'Actualiza' (updates), the resource 'tarjeta' (card), and the specific fields (name, status, assignee, props), distinguishing it from siblings like 'roiq_add_card' and 'roiq_move_card'.

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 this tool versus alternatives (e.g., when to update vs move a card), nor any conditions or prerequisites.

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