Refresh Mega MGC Coffee store cache

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

Without annotations, the description carries full burden. It mentions fetching and saving to cache but omits behavioral details like whether the cache is overwritten, idempotency, or side effects. The tool likely writes data, yet no disclosure of that.

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 a single concise sentence that efficiently conveys the core action. It is front-loaded but could include more structure or detail without becoming verbose.

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 no output schema and 2 well-documented parameters, the description is adequate for a simple refresh. However, it lacks information on return values, success indicators, or failure behavior, which would help an agent.

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%, so baseline 3. The description adds no extra meaning beyond what the schema provides for 'cachePath' and 'maxStores'. It does not explain parameter semantics or defaults.

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 clearly states the action ('Fetch all Mega MGC Coffee app stores and save them to the local JSON cache') with a specific verb and resource. It distinguishes from sibling tools like checking stock or finding stores, which focus on different operations.

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 for cache refreshing but lacks explicit guidance on when to use this tool versus alternatives. No exclusions or context for selecting among siblings are provided.

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