getIssueCategories

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'List issue categories', which implies a read-only operation but does not disclose any specifics such as required authentication, response format, potential errors, or whether it returns all categories at once. No additional behavioral context is provided.

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 a single, short sentence that is concise and front-loaded with the main action. It avoids wordiness, but the extreme brevity sacrifices instructional value. It earns its place by stating the core purpose without padding.

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 absence of an output schema and annotations, the description is severely incomplete. The tool has nested input objects and two required parameters, yet the description provides only a terse phrase with no information on return values, response structure, pagination, or error behavior. It is not sufficient for an agent to understand the tool's full behavior.

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 schema has 0% description coverage, and the description itself does not mention any parameters. It fails to explain the required pathParams (format, projectId) or the optional nometa query parameter. The description adds no value beyond what the schema already exposes, which is nearly nothing in terms of semantic guidance.

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 'List issue categories' is a clear verb+resource statement that accurately identifies the operation. It distinguishes from sibling tools like getIssueCategory (singular) and create/update/delete variants by using 'list' to imply plural retrieval. However, it does not explicitly mention that it operates per project, which is a key scoping detail.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that it lists categories for a specific project via projectId, nor does it differentiate from getIssueCategory or other list-type tools. The description offers no context for choosing this tool.

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