zyta_expedientes_alertas_update

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

With no annotations, the description carries full burden but only states the update action. It fails to disclose side effects, authorization needs, or that it is a PATCH operation (only hinted in endpoint). Very little behavioral insight.

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 concise (a single short sentence), but it lacks structure. It could be expanded to include essential details without verbosity. As is, it is adequate but sparse.

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 (7 parameters, no output schema, low schema coverage), the description is incomplete. It does not specify which fields are updatable, return values, or prerequisites. The mention of 'PATCH .../alertas/:id' provides minimal endpoint context but not enough.

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 14%, and the description adds minimal parameter meaning (only hints at 'estado' via the example). The other 6 parameters are not explained, leaving significant gaps.

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 updates an alarm ('Actualiza alarma') and gives an example ('resuelta'), which distinguishes it from sibling create/delete/list tools. However, it does not specify that it performs a partial update (PATCH), leaving some ambiguity.

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 the create or delete siblings. The description lacks context for selection.

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