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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known before reading the description. The sentence 'triggers cannot be changed with this server' largely restates readOnlyHint rather than adding new behavioral context; no pagination or result-shape behavior is disclosed beyond the GET /trigger endpoint. Some added value, but not enough for a 4.

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?

Two short sentences, zero filler, with the resource and scope front-loaded before the read-only constraint. Every clause contributes.

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?

For a parameterless-filter list tool this is close to adequate, and annotations cover safety. However, with no output schema, the description should say more about the returned shape (e.g. that results are paginated via next_skip), which is currently left entirely to the input schema.

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 100%, so skip, sort, and limit are already fully documented including defaults and use of next_skip. The description adds no parameter meaning, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb (List) and resource (automation triggers), and enumerates the trigger kinds (event, rental, template, delay), which tells an agent precisely what domain object is returned. No sibling tool covers triggers, so there is no ambiguity to resolve.

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 the usage context (inspect automation triggers) but never states when to prefer this over alternatives or what prerequisite conditions apply. The 'read-only' note hints at the boundary of the tool, but there is no explicit when/when-not guidance.

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