get_next_available_issue

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: 'Returns the highest priority available issue of the specified type,' 'Does not modify task status or claim ownership,' 'Finds issues that are ready to work on (all prerequisites complete),' and details on return formats for success, no issues, and errors. This covers safety (non-modifying), prioritization logic, and error handling, though it doesn't mention rate limits or authentication needs.

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 well-structured with clear sections (Behavior, Available issue types, Required parameters, Usage patterns, Return format) and front-loaded key information. It's appropriately sized for the tool's complexity, but some redundancy exists (e.g., repeating 'Essential for discovering' in the opening and closing). Most sentences earn their place by adding value, though it could be slightly more concise.

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 tool's moderate complexity (2 parameters, no output schema, no annotations), the description is largely complete. It covers purpose, usage, behavior, parameters, and return formats. However, without an output schema, it doesn't detail the structure of the 'complete issue object' returned on success, which could leave gaps for an agent interpreting results. It compensates well with behavioral details but has minor omissions.

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 baseline is 3. The description adds significant value beyond the schema: it explains the meaning of 'issueType' with available types and their hierarchy ('Top-level containers', 'Large features within projects', etc.), provides context for 'scope' with examples ('Limits search to issues within a specific project or area'), and includes usage patterns that clarify how parameters interact. This enhances understanding beyond the schema's enum and description.

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: 'Gets the next available issue of a specific type' and 'Essential for discovering what work is available when you're ready to start on a new project, epic, feature, or task.' It specifies the verb ('Gets', 'find') and resource ('issue'), and distinguishes from siblings like 'list_issues' by focusing on the 'next available' issue based on priority and readiness.

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 explicitly states when to use this tool: 'Use this tool to find the next available issue that's ready to work on' and 'Essential for discovering what work is ready to be done.' It provides clear usage patterns with examples (e.g., 'Find next project to work on: issueType='project''), and distinguishes it from alternatives by noting it 'Helps you discover what work is available without having to browse through all issues,' implying it's preferable over 'list_issues' for this specific use case.

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