manage_event

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

The description explicitly lists a delete action while the annotations declare destructiveHint=false. This is an annotation contradiction: delete is semantically destructive, so the agent cannot trust the stated safety profile. No additional behavioral context is provided about side effects, confirmation requirements, or external changes.

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 and front-loads the resource and action list, with no filler. However, it is telegraphic and omits crucial operational context, so its brevity is not a strength in this case.

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?

This is a multi-action tool with five parameters, conditional relationships among actions and fields, and open-world side effects. The description provides almost none of the needed context for correct invocation, making it inadequate for an agent to use reliably.

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 0%, and the description does not explain title, event_id, event_type, or confirm_hash. It only repeats the action names already present in the schema enum, so the agent cannot determine which parameters are needed for each action or what confirm_hash is for.

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 identifies the domain ('Conversion events and pixels') and explicitly enumerates the supported actions. It is clear enough to distinguish the tool from its non-event siblings, though it relies on the tool name rather than a fully formed verb+resource sentence.

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?

The domain label gives the agent a general sense of when to use the tool, but there is no guidance on which action to choose under which conditions, nor any indication of why this tool is preferable to alternatives. Usage is implied rather than explicit.

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