list_all_issues

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

No annotations provided, so description must fully disclose behavior. It only mentions global search and no project_id needed, but omits read-only nature, permissions, pagination, or output structure.

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?

Two sentences are very concise but omit critical details about parameters and usage. Conciseness here sacrifices necessary information, making it ineffective for correct tool invocation.

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 4 parameters with no schema descriptions, no annotations, and an output schema present, description fails to cover parameter semantics, usage context, or behavioral traits. Highly incomplete for a global search tool.

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 0%, and description gives no explanation of any parameter (filters, platform, limit, state) beyond stating no project_id needed. Agents lack essential information to use parameters correctly.

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?

Description explicitly states 'List issues across all projects (global search)', clearly indicating the verb (list) and resource (issues) with scope. Differentiates from siblings like 'list_issues' by noting no project_id needed.

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?

Implies use for global search without specifying a project, providing clear context. However, no explicit when-not-to-use or comparison with similar tools like list_issues or list_my_issues.

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