Add Issue

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

With no annotations provided, the description carries the full burden. It only says 'Create a new issue' and provides description formatting advice, but doesn't disclose side effects, return values, prerequisites, or default behaviors. This is insufficient for a create tool.

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 two sentences, front-loaded with the primary purpose, and includes only essential guidance. No wasted words.

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?

The tool has 7 parameters and many sibling tools, but the description is minimal. It doesn't distinguish itself from batchCreateIssues or explain its role in the broader workflow. However, the schema and output schema cover the technical details, so the description is adequate for basic use but lacks richer context.

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?

All parameters are documented in the schema (100% coverage), so baseline is 3. The description adds a structured format for the description field (1-2-3 list), which is slightly more specific than the schema's 'implementation details, approach, and acceptance criteria,' but it's marginal.

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 creates a new issue in Panel Todo Pro, using a specific verb and resource. This distinguishes it from sibling tools like panelTodo_updateIssue and panelTodo_batchCreateIssues, though it doesn't explicitly reference them.

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 specific guidance for sprint planning, instructing what to include in the description field. However, it does not explicitly state when to use this tool over alternatives like batchCreateIssues, nor when not to use it. The guidance is context-specific but not a full usage guideline.

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