List Forms answer integrations

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine return-shape context absent from annotations: each entry carries the run's status and its type field (issue_key, link, to_address, url, ...), and it routes the agent to notifications_get for the full run detail.

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?

It is short and front-loads the resource, but the first sentence is awkwardly worded and requires re-reading, and the two clauses about entry fields and notifications_get are compressed to the point of ambiguity. No wasted padding, but clarity suffers for the size.

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 no output schema, the description is the only source of return-value information, and it does partially cover that (status, type field) plus where to get full detail. However, it never clarifies ordering, pagination, or whether a missing run is returned, leaving gaps for an agent that needs to interpret the list.

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%, so the baseline is 3, but the description adds a constraint the schema does not express: exactly one of answer_id or answer_key must be supplied ('one of them'). The schema marks both as optional with null defaults, so this clarification is real added semantics beyond the structured field descriptions.

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 identifies the resource as integration runs triggered by an answer and states the two filter inputs, so an agent can tell it lists per-answer integration activity rather than the answers themselves. The opening sentence ('The integration runs one answer triggered, by answer_id or answer_key') is grammatically garbled, which slightly blunts an otherwise clear verb+resource statement.

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?

It implies usage by saying the runs are triggered 'by answer_id or answer_key (one of them)', and it points to notifications_get for the full run, which is a mild alternative pointer. But there is no explicit when-to-use/when-not statement or condition distinguishing this summary listing from other forms_answers_* siblings.

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