list_service_change_events

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

Annotations already declare readOnlyHint and idempotentHint. The description adds behavioral context such as filtering by date range (since, until) and team/integration IDs, and states it returns a list of ChangeEvent objects. This goes beyond the annotations by detailing query capabilities.

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 front-loaded with a clear one-liner, followed by a structured list of parameter docs. It is reasonably concise, though the parameter docs could be slightly more compact. Every sentence adds value.

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?

With 8 parameters, 1 required, and an output schema (exists), the description covers all parameters and return type. It lacks explicit pagination details beyond limit/offset, but output schema likely handles that. The annotations cover safety. Overall, complete enough for a list tool.

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%, so the description carries the full burden. It provides detailed explanations for all 8 parameters, including their purpose (e.g., 'The start of the date range', 'Set to True to include total count'), adding significant meaning beyond the schema's types and defaults.

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 'List all change events for a specific service,' specifying the verb (list), resource (change events), and scope (for a specific service). This distinguishes it from sibling tools like 'list_change_events' (no service filter) and 'get_change_event' (single 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 implies usage when you have a service_id by listing it as a required parameter, but does not explicitly state when to use this tool versus alternatives like 'list_change_events'. No guidance on when not to use it or prerequisites beyond providing a service_id.

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