tm

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It lists many methods with their required/optional parameters, clearly indicating write operations (e.g., issueCreate) and read operations (e.g., issueList). It does not explicitly mention side effects, authentication, or rate limits, but the method names and parameter descriptions provide reasonable transparency.

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 quite long and dense, listing many methods inline. It front-loads the main purpose but then dumps a large block of method details. While this ensures completeness, it sacrifices conciseness and readability. A more structured format (e.g., bullet points or separate lines) would improve it.

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 complexity (many methods, nested params) and no output schema, the description is very complete. It covers all primary methods and their parameters, even providing a way to get full schema via 'list'. However, it lacks explicit descriptions of return values for each method, which would be needed for full completeness.

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?

The input schema covers both parameters (method and params) with descriptions, achieving 100% coverage. The description adds significant value beyond the schema by enumerating possible method values and their specific parameter signatures, helping the agent understand what to pass in 'params'. The examples and method listing enhance parameter semantics.

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 that the tool is for task management, listing specific entities (projects, issues, tasks, etc.). It provides a detailed breakdown of methods, making the purpose unmistakable. It distinguishes from sibling tools like 'as', 'comm', etc., by its domain-specific content.

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 explains how to call the tool (with method and params) and suggests using 'list' for full method details, but it does not provide explicit guidance on when to use this tool over sibling tools or alternatives. The context is clear but lacks exclusionary guidance.

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