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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the baseline is covered. The description adds real behavioral context not found in annotations: imported text is untrusted content and no order addresses or payment credentials are returned, which is useful for both security and expectation-setting.

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 three short sentences and front-loads the purpose before the security caveats. There is little wasted text, though the first sentence is somewhat vague rather than crisp.

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 tool with rich annotations, the description covers safety and sensitive-data exclusions but omits what the store_id parameter means and what 'missing sale-critical facts' actually refers to. It is adequate but not complete.

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 only parameter, store_id, is not mentioned in the description. The description does not explain that the draft retrieved is scoped by store_id, so it adds no semantic meaning beyond the bare schema type.

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 states a specific verb, 'Read', and a resource, 'saved catalog and missing sale-critical facts', but never explicitly says this is a store draft or ties it to the tool name. An agent can guess the domain, but it is not clearly distinguished from siblings such as get_website or get_booking_draft.

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?

There is no guidance on when to use this tool instead of alternatives like get_website, save_store_draft, or create_store_draft. The read-only nature is implied, but no selection conditions or exclusions are stated.

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