getIssueCategories

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

The readOnlyHint annotation already declares the tool is read-only, which lowers the bar. However, the description adds no behavioral context at all—no mention of what is returned, whether authentication is needed, if it requires a project, or how format/nometa affect the response. It contributes nothing beyond what the annotation already provides.

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 with no wasted words, which is appropriate for conciseness. However, it is minimal to the point of under-specification; still, for the conciseness dimension alone, it is efficient and front-loaded with the core action.

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 requires two path parameters (format and projectId) and has a nested schema, and there is no output schema to aid understanding, the description is completely inadequate. An agent cannot determine how to invoke the tool correctly, what the response looks like, or why the query parameter exists.

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%, so the description must compensate by explaining parameters. It does not mention projectId, format, or nometa, leaving the agent unaware of the required path parameters and the optional query parameter. This is a critical failure for parameter understanding.

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' states a clear verb and resource, so an agent understands the basic action. However, it fails to mention that categories are scoped to a project (as required by the projectId parameter), and it does not differentiate from the singular 'getIssueCategory' sibling, leaving some ambiguity about scope and cardinality.

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?

There is no guidance on when to use this tool versus alternatives such as getIssueCategory, createIssueCategory, or getIssueStatuses. The description does not mention any context, prerequisites, or exclusions, so the agent has no basis to select this tool over its siblings beyond the name.

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