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

The annotations declare readOnlyHint=false, which would otherwise look contradictory for a 'get' tool; the description resolves this by disclosing that a one-time extraction may be started, a real side effect. It does not say what happens on subsequent calls or how long extraction takes, despite idempotentHint=false and no output schema.

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?

Three short sentences with the contents, the use case, and the edge-case behavior in that order; nothing is repeated or wasted, and the core purpose is front-loaded.

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 usefully enumerates the return contents, and it flags the extraction side effect that the annotations imply. It is nearly complete for a one-parameter tool, with minor gaps around repeat-call behavior and the latency of a fresh extraction.

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 single optional 'store' parameter is fully documented in the schema (100% coverage), including the omit-when-one-store rule, so the schema does the heavy lifting. The description adds no additional meaning about the parameter or selection behavior across multiple connected stores.

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?

States a specific verb and resource ('Read the store's design guide') and enumerates exactly what it returns: colours, typography, spacing, components and brand voice. It is not differentiated from the similarly named sibling 'read_guide', so an agent must infer that distinction rather than being told.

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?

Gives clear context for use ('when designing or reviewing pages') and a condition for the non-obvious extraction path ('With no guide yet and a distinctive theme'). It does not name an alternative tool or state when not to use it, so the bar for a 5 is not met.

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