getIssueCategory

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

With no annotations, the description carries full burden for behavioral disclosure. It omits any mention of the tool's read-only nature, required permissions, rate limits, or return value structure, providing minimal 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?

At two words, the description is overly terse. While concise, it sacrifices essential context and structure that would aid an AI agent in selecting and invoking the tool correctly.

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 nested parameters, no output schema, and a large set of sibling tools, the description is completely inadequate. It fails to explain the response format or how this tool fits into broader workflows.

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 description adds no meaning to the two sub-parameters (format and issueCategoryId) beyond what the schema provides. Since schema coverage is 0%, the description should at least explain their purpose, but it does not.

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 'Show issue category' is a tautology, restating the tool name without adding specificity or distinguishing it from siblings like 'getIssueCategories'. It fails to clarify that it retrieves a single category by ID.

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 (e.g., 'getIssueCategories' for listing). There is no mention of prerequisites, such as the need for a valid issue category ID, or when not to use it.

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