track

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about the destructive/reversible nature of archive and delete, required permissions, or side effects. Listing action names conveys what operations exist but not their behavioral consequences.

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?

A single short sentence with no wasted words, and the resource is front-loaded before the action list. It is efficiently sized, though the brevity comes at the cost of detail.

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?

This is a 17-parameter, five-action multi-tool with no annotations and no output schema, so the description should clarify how parameters map to actions and flag destructive operations. Instead it provides only an action list, leaving the agent to reconstruct per-action semantics from the schema alone.

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 88%, so the schema already documents the parameters well (e.g., content for create, brief/limit/issue_id for list). The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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 names a clear resource (issue tracking) and enumerates the five actions the tool performs (create/update/archive/delete/list), so an agent can grasp the tool's scope. It does not differentiate from siblings like task or status, but the verb+resource pairing is specific.

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 only lists the available actions; it gives no guidance on when to use this tool versus siblings such as task or status, and no conditions or prerequisites for choosing a given action. Usage must be inferred entirely from the bare action names.

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