pylon_get_issue_messages

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

With no annotations, the description must fully disclose behavior. It says 'all messages' but the schema's limit parameter with a default of 100 suggests pagination, making 'all' potentially misleading. No mention of return format, ordering, auth, or pagination behavior. The lack of transparency around the 'all' claim is a significant gap.

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 a single concise sentence with no wasted words. It is front-loaded with the verb and resource, and every word contributes to understanding the tool's purpose.

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 lack of output schema and annotations, the description should provide more context. It does not explain return structure, pagination, or the fact that 'all' may require multiple calls. For a tool with 3 parameters and a potential gap between 'all' and the default limit, this is insufficient.

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 the schema already provides complete parameter meanings. The description adds no additional parameter semantics. Baseline 3 is appropriate because the schema carries the full explanatory burden and does so adequately.

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 'Get all messages for a specific issue' uses a specific verb ('Get') and resource ('messages for a specific issue'), clearly distinguishing it from sibling tools like pylon_get_issue (issue details) and pylon_list_issues (list issues). The purpose is unambiguous.

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 context—use when you need messages for a particular issue—but provides no explicit guidance on when not to use it or alternatives. Sibling tools have similar names, yet no differentiation is mentioned. The context is clear but not elaborated.

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