pylon_get_issues

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

No annotations are provided, so the description carries full burden. It mentions what the tool returns (list of issues with details) but lacks critical behavioral information: whether this is a read-only operation, if it requires authentication, rate limits, pagination behavior (beyond the 'limit' parameter), or error conditions. The description doesn't contradict annotations (none exist), but provides minimal behavioral context.

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 appropriately concise (two sentences) and front-loaded with the core purpose. The second sentence adds useful context about use cases. No wasted words, though it could be slightly more structured by separating purpose from usage guidance.

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 no annotations and no output schema, the description provides basic purpose and usage but lacks completeness for a tool that returns data. It doesn't describe the return format in detail (beyond listing some fields), error handling, authentication requirements, or how results are ordered. For a read operation with 3 parameters, this is minimally adequate but has clear gaps.

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 fully documents all three parameters (assignee, status, limit) with descriptions, examples, and constraints. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline of 3 when schema coverage is complete.

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 the tool's purpose: 'Get support issues/tickets from Pylon' with specific details about what it returns (list with title, status, priority, assigned team member). It distinguishes from sibling 'pylon_get_issue' (singular) by implying this returns multiple issues, but doesn't explicitly differentiate from 'pylon_search_issues' which might have overlapping functionality.

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 provides some usage context: 'Use this to see your workload or find specific issues.' This implies when to use it (monitoring workload, finding issues) but doesn't explicitly state when to choose this tool versus alternatives like 'pylon_search_issues' or 'pylon_get_issue'. No exclusions or prerequisites are mentioned.

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