agregar_invitado

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

Annotations already indicate this is a mutating but non-destructive operation, and the description aligns with that. It adds a little context by mentioning a personalized link and number of places, but it does not disclose side effects, requirements, or what happens on success.

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 a single, direct sentence that front-loads the action. There is no wasted text or redundancy.

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?

The tool has three flat parameters and no output schema, so the description should carry more weight. It is incomplete because it omits the meaning of the required invitacion_id parameter, does not clarify how the custom link is generated or supplied, and gives no selection guidance relative to sibling tools.

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?

With 0% schema description coverage, the description must compensate, but it only hint at 'número de lugares' for lugares. It does not explain the required invitacion_id parameter or the nombre parameter, and 'link personalizado' does not map to any actual parameter in 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 the action ('Agrega un invitado') and the resource, which distinguishes it from listar_invitados and ver_invitacion. However, it does not explicitly distinguish it from crear_invitacion, and the mention of 'link personalizado' is not reflected in any schema parameter.

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?

There is no guidance about when to use this tool versus alternatives like crear_invitacion or editar_invitacion. The description does not mention prerequisites, such as needing an existing invitacion_id, or scenarios that would make this tool inappropriate.

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