Get store

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds no additional behavioral context such as response shape, not-found behavior, or permission requirements. It is consistent with the annotations but does not go beyond them.

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 single sentence is entirely functional, front-loads the action and object, and contains no filler or repetition. It is an appropriate size for a simple getter.

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 one-parameter read-only getter with annotations covering the safety profile, 'Fetch one store by id' is nearly complete. It lacks explicit return or error details, but those are less critical for such a simple invocation.

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 0%, and the description only echoes that the tool fetches by id rather than explaining the store_id format or meaning beyond the property name. The schema already shows store_id is a required string, so the description adds very little semantic value.

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 'Fetch one store by id' names a specific verb (fetch), a resource (store), and the selecting key (id), making it clearly distinct from sibling list_stores. An agent can tell this is a singular retrieval operation with no ambiguity.

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 only usage cue is the implicit implication that a store_id is needed to retrieve one specific store. There is no explicit statement about when to use this versus list_stores or other getters, so the agent must infer the right context.

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