eventstream_get_definition

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

Annotations already mark the tool as read-only and non-destructive. The description adds that 'Authentication is handled transparently using Azure Identity,' which is useful context beyond annotations. However, it does not disclose any other behavioral traits (e.g., caching, pagination, or error behavior), and annotations already cover the key safety aspects, so the incremental value is moderate.

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 short (two sentences plus param docs) and front-loaded with the core purpose. It avoids unnecessary fluff. The param documentation follows a clear pattern. Slightly wordy due to Rust-style doc comment syntax, but still efficient. Every sentence earns its place.

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 tool's low complexity (2 required params, output schema present, readOnlyHint in annotations), the description covers the essential purpose and authentication behavior. It could mention what 'definition' includes (e.g., JSON structure) or any limitations, but for a simple getter with an output schema, it is sufficiently complete.

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%, but the description provides basic parameter documentation ('workspace_id: The workspace ID (UUID), item_id: The eventstream item ID (UUID)'). This adds meaning beyond the raw schema (which only has titles and types), but it is minimal—lacking format constraints, examples, or any deeper semantics about how IDs are used or validated.

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 'Get the definition of an Eventstream item', which is a specific verb-resource combination. It effectively distinguishes from sibling tools like eventstream_get (likely retrieving metadata) and eventstream_get_current_definition (retrieving only current), providing unambiguous purpose.

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 provides no guidance on when to use this tool versus alternatives like eventstream_get or eventstream_get_current_definition. With 18+ eventstream-related siblings, explicit context about choosing this over others is missing, making it hard for an AI to select optimally.

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