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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety bar is mostly covered. The description adds value by disclosing what the response contains (full configuration with type-specific fields), which matters since there is no output schema; it does not cover not-found/error behavior or any permission requirements.

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 sentences, front-loaded with the action, then the return payload, then the usage trigger. Every clause carries information and nothing is repeated from the schema or annotations.

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 simple two-parameter read tool whose annotations cover the safety profile, the description supplies the essentials: what is fetched and why. The remaining gap is the unmentioned webinarId scoping, which is the one thing an agent could still get wrong.

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 must carry parameter meaning, and it only implies interactionId via 'by ID'. The required webinarId — and the constraint that the interaction must belong to that webinar — is never mentioned, leaving half the inputs unexplained beyond their names and UUID format.

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?

Uses a specific verb and resource ('Retrieve one interaction by ID') and enumerates the returned configuration (timing, headline, internal name, type-specific fields). The singular 'one ... by ID' implicitly separates it from the list/find_matching siblings, though no sibling is named explicitly.

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?

Gives a concrete use case: inspect a poll or CTA before updating or deleting it, which maps naturally onto the interactions_update and interactions_delete siblings. It stops short of saying when to prefer interactions_list or interactions_find_matching instead of ID lookup.

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