ah_get_sub_categoriesRetrieves child subcategories for a specified supermarket category ID so you can navigate product categories. Results are cached for up to 24 hours.
Fetch child subcategories for a specific supermarket category ID. Cached for up to 24 hours.
| Name | Required | Description | Default |
|---|---|---|---|
| category_id | Yes | Category ID to retrieve subcategories for |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the safety profile is covered, and the description adds a genuinely non-obvious trait: results are cached for up to 24 hours, warning about staleness. It does not cover failure behavior for invalid IDs or result ordering, keeping it short of a 5.
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?
Two sentences, zero waste, with the core action front-loaded and the caching caveat as a compact second sentence.
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 single-parameter read with annotations covering safety and no output schema, this is nearly complete. The one residual gap is that nothing tells the agent where a valid category_id comes from.
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 coverage is 100% and the single parameter is fully documented, so baseline 3 applies. The description reinforces that the ID refers to a supermarket category but adds no format, type, or sourcing details beyond the schema.
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?
States a specific verb ("Fetch") and resource ("child subcategories") scoped to a supermarket category ID, which clearly separates it from ah_get_categories' implied top-level listing. It stops short of naming the parent-category sibling explicitly, so differentiation is inferable rather than stated.
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?
Usage is only implied: an agent can infer this is the drill-down step after obtaining a category ID, but the description never says when to use it versus ah_get_categories, nor that a category_id from that tool is a prerequisite. No exclusions or alternatives are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.