get_category

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

The readOnlyHint annotation already indicates a safe read operation. The description adds behavioral context that the response includes description and product count, and that the fields param can limit the response. This goes beyond the annotation and clarifies the return data scope.

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 two sentences, front-loaded with the action and resource. The first sentence states the core purpose, and the second sentence gives a single actionable hint. No wasted words.

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?

The description is sufficient for a simple read operation. It covers the tool's purpose and key return contents. The fields param's default list in schema provides additional response structure. It lacks an explicit statement that a single object is returned, but this is implied by 'a category' and the get_ naming convention.

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%, so baseline is 3. The description adds a tip to use the fields param to request only needed fields, but this is not a new semantic beyond what the schema's param description already states. No further parameter meaning is added.

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 uses the specific verb 'Get' and resource 'category', and clarifies scope with 'full details including description and product count'. It clearly distinguishes from sibling list_categories, which is a list operation, making the 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 implies usage when a single category's full details are needed, but it does not explicitly contrast with list_categories or state when to use this tool instead. It does provide guidance for the fields param, which is a useful usage hint, but lacks explicit alternative comparison.

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