List issue thread interactions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds the HTTP method (GET) and authorization class (board_or_agent), which are not in annotations. However, it does not discuss error behavior, pagination, or other runtime aspects.

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 very concise with two sentences. It is front-loaded with the core purpose and adds the HTTP method and auth class. While efficient, it could include more detail without becoming lengthy.

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?

Given the presence of an output schema and clear annotations, the description sufficiently conveys the tool's function. It explicitly states it lists interactions for a specific issue. Minor gap: does not explicitly state that the 'id' is the issue ID, but that is easily inferred.

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?

The input schema has 0% description coverage, and the description does not explain the 'path' parameter or the 'id' field. Although the parameter is obvious from the tool name and context, the description fails to add explicit meaning to the schema.

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 it lists issue thread interactions, using a specific verb 'List' and resource 'issue thread interactions'. It distinguishes from siblings like pc_post_issues_by_id_interactions (create) and pc_get_issues_by_id_interactions_by_interaction_id_accept (accept a specific interaction).

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 for listing interactions but provides no explicit guidance on when to use this vs alternatives, such as when to use pc_get_issues_by_id for issue details or other interaction-related tools. No exclusions or context are given.

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