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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds what the agent cannot get elsewhere: this returns narrative fields plus a conditional campaign object with dates and an open/closed status. It does not say what happens when the category or campaign is absent.

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 dense sentences with no filler. The payload contents are front-loaded and the cross-tool pointer is placed last, which is the right priority order.

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?

With no output schema, the description has to carry the return-shape burden and it largely does, listing the fields and the conditional campaign block. Minor gaps remain around empty/missing results, but for a read-only two-parameter lookup this is close to sufficient.

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 both required parameters are documented with their source fields (find_store/search_products and list_categories). The description adds a small amount of meaning by noting the id is shared with browse_products, but nothing about format or validation beyond the schema's maxLength.

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?

It names the resource (one store category) and enumerates the returned payload: description, image, subcategories and campaign data. It also distinguishes itself from browse_products by handing product retrieval off to that sibling. The only gap is that the retrieval verb is implied by the name 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 implied rather than stated: fetch a single category by id. The one explicit routing hint is that products come from browse_products with the same id, which is a genuine alternative pointer. There is no guidance on when to use this versus list_categories or get_store_info.

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