get_workflow_event

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

The description mentions 'decoded payload fields when present', giving some insight into response processing. However, with no annotations, it fails to disclose important traits such as read-only nature, error behavior (e.g., if event not found), or any side effects.

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?

A single sentence that efficiently conveys the tool's purpose and a key behavioral detail. It is front-loaded and avoids redundancy, though it could be slightly expanded for completeness.

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 description is minimal but covers the primary function. Given there is no output schema, it would benefit from mentioning the return structure or linking to related tools like get_workflow_history.

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?

All 3 parameters have descriptions in the input schema (100% coverage), so the description does not need to add parameter details. It does not add any new meaning 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 the verb 'Get' and the resource 'single workflow history event', and adds specificity with 'decoded payload fields when present'. This effectively distinguishes from siblings like get_workflow_history which lists multiple events.

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 on when to use this tool versus alternatives like get_workflow_history. The description does not provide context for when this single event retrieval is appropriate or mention prerequisites or limitations.

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