get_single_category

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

Annotations already declare readOnlyHint=true, so the description correctly adds the behavioral nuance that category groups return a list of children categories. This is extra context beyond the read-only flag, though it doesn't address additional behavior like error responses or nonexistent IDs; with annotations covering safety, this is adequate.

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 16-word sentence that front-loads the main purpose and immediately states the key qualifier about category groups. No redundant content.

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?

For a simple one-parameter read tool with readOnlyHint=true and no output schema, the description covers what the tool returns (details plus children for groups) and the parameter is fully documented in the schema. It could be more explicit about the shape of 'details,' but nothing essential is missing.

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 100%, and the schema already explains categoryId and instructs to call get_all_categories first. The tool description adds no param-specific meaning, so it meets the baseline 3 for high schema coverage.

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?

Description states a specific verb ('Get details') and resource ('single category or category group'), and differentiates from siblings like get_all_categories by noting it returns a single item. The mention of children categories for groups adds further specificity, making the tool's purpose unambiguous.

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 implicitly conveys when to use it (when you need details on one category) and explicitly advises calling get_all_categories first to discover ids. It does not explicitly exclude alternatives or name sibling tools, but the context is clear enough; falls short of a 5 because no when-not-to-use guidance is given.

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