Run the store review

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

Annotations declare readOnlyHint=false, openWorldHint=true and idempotentHint=false but give no operational detail. The description discloses the 30-minute per-project rate limit and 429 response, the write semantics (records a gate run), the non-submission guarantee, and the three-valued result semantics including that 'unknown' means never checked.

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?

Dense but front-loaded: the action and scope land first, then result semantics, guardrails and return shape. Some sentences are long, but every clause carries new information rather than restating the schema.

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?

No output schema exists, yet the description enumerates the return keys and names get_store_status for later retrieval. It omits per-check detail and remediation, which are plausibly covered by upstream tools, so it is nearly complete rather than fully self-contained.

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% and the schema already documents projectId including the server-configured default and project_id alias, so the description's 'Optional projectId' merely confirms what the schema carries. Baseline 3.

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 ('Run the store review for one project now') and enumerates exactly what is checked: listing text, claims, privacy labels, screenshots, length limits, checklist. The sibling get_store_status is named as the read counterpart, so an agent can distinguish them.

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?

Explicit about when to use (run a review now) versus the alternative (get_store_status to read it later), includes the 429/30-minute rate limit and the 'not legal advice' scope caveat, and notes that nothing is submitted to a store.

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