zyta_expedientes_registrar_actuacion

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

Discloses that the AI will choose the case if expedienteId is missing, which is a key behavioral trait. However, no annotations exist, so the description carries full burden; it does not address destructiveness, authorization, or success behavior.

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?

Two sentences with no waste. The endpoint is included for clarity. Information is front-loaded and relevant.

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?

Covers the core functionality and the AI selection trait, but lacks any mention of return values or error conditions. Without an output schema, the description should hint at what happens after registration.

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 covers 100% of parameters. The description adds context about the AI choosing case when expedienteId is absent, but does not explain link or message parameters beyond the schema.

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 registers an action in a case without portal, with a specific verb and resource. It distinguishes from siblings (no other 'registrar' tool), but could be more explicit about its unique role.

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?

Implies usage for cases without portal, but provides no explicit when-to-use or when-not-to-use guidance. No alternatives mentioned, leaving the agent to infer context.

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