fire_event

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

The description adds one behavioral trait (the WRITE_ENABLED requirement) beyond the annotations. However, it does not detail side effects, return behavior, or state changes, which would be valuable for a write operation.

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, efficient sentence with no redundancy or extraneous information. It is well-structured for quick comprehension.

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 5 parameters, annotations including openWorldHint=true, and no output schema, the description provides the core purpose and a key requirement but lacks details on side effects, asynchronous behavior, or what the tool returns. It is adequate but not fully comprehensive.

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?

The input schema already covers all 5 parameters with descriptions (100% coverage), so the description does not need to add parameter details. It adds no additional parameter semantics.

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 'Fire' and the resource 'custom ServiceNow event for a specific record'. It distinguishes from sibling tools like 'register_event' by specifying the action of firing an event.

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 description explicitly states a prerequisite condition 'requires WRITE_ENABLED=true', providing clear guidance on when the tool is applicable. However, it does not mention when to avoid using it or suggest alternatives.

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