get_store

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

With no annotations provided, the description must carry the transparency burden. It usefully discloses that the 'reason' argument is required for audit, and gives format examples for store_id. However, it does not explicitly state whether the operation is read-only, whether special permissions are needed, or any limitations on returned details, relying on the output schema to clarify output.

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 compact and front-loaded: one sentence states the core purpose, followed by a clean args list. Every sentence adds value with no redundancy or filler.

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 the simple get-by-id operation, an output schema is present, and the description includes the audit requirement, the tool is well-specified. It could have strengthened contextual guidance by explicitly referencing list_stores for discovering store_ids, but this is a minor omission for a low-complexity tool.

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?

The schema has no descriptions (0% coverage), so the description provides essential meaning for both parameters. It clarifies 'store_id' with an example format and explains 'reason' as an audit requirement, going well beyond the bare schema field names.

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 ('Get details'), the resource ('a single store'), and the required identifier ('store_id'). The qualifier 'single' distinguishes it from sibling tool list_stores, 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 you have a known store_id and need just that store's details, contrasting with list_stores. It does not explicitly mention alternatives or exclusions, but the by-id framing provides clear context for when this tool should be selected.

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