event_info

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

No annotations are provided. The description says 'Get...' but does not state read-only/no side effects. It is a simple getter, but with the absence of annotations the description does not carry the full safety/error context.

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?

One sentence plus input schema, all of which is needed; no filler.

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?

Tool has only a minimal getter with one parameter; it describes returned fields but lacks output schema, error behavior, not-found case, or relation to sibling retrieval 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?

The description gives the accepted formats for 'target' (event:// path or {guid}), compensating for the schema description that just says 'string'. It explains format but not overlapping semantics for constraints.

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?

Description uses specific verb+object ('Get an event's guid, name, path and maxVoices'), with the target parameter format described. However, it does not explicitly differentiate from sibling event tools.

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?

Context of use is implied by the tool name and event-specific parameters, but no explicit guidance is given on when to choose this over sibling event_get_* tools.

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