Show New Change Event

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

The description contains an internal inconsistency: it first implies a single resource ('fetch the full details of a specific Change Events by its identifier') but then states 'Returns a paginated JSON array of Change Events,' suggesting a list. Annotations (readOnlyHint, etc.) are consistent, but the contradictory behavior reduces transparency.

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 relatively concise (5 sentences) and front-loads the purpose. It includes helpful but non-essential details like the API endpoint. Slightly verbose with repeated 'Change Events' but acceptable.

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?

No output schema is provided, yet the description only says 'returns a paginated JSON array of Change Events' without specifying fields or structure. The inconsistency between single vs. multiple resources is a significant gap. Given the complexity and many siblings, more details are needed.

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 coverage is 100%, and the description adds minimal value beyond schema descriptions. It notes that project_id is required and page/per_page control pagination, but this is already inferable from the schema or basic usage.

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 tool's purpose: 'Show default attributes for a Change Event' and 'fetch the full details of a specific Change Events by its identifier.' It specifies the resource (Change Events) and action (show/fetch), distinguishing it from other show 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?

The description explains when to use the tool (fetch details by identifier) and mentions pagination parameters, but it does not provide guidance on when not to use it or how it differs from the sibling 'show_change_event' (without 'new'). Explicit alternatives or exclusions are missing.

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