Set store review intake

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

Annotations only say this is a non-read-only, idempotent, non-destructive, open-world write; the description adds the materially important context that enabling has an auth bypass barrier (403 HUMAN_REQUIRED) and why (it decides public reviews become reports), plus the API-key vs console asymmetry. That is real behavioral disclosure beyond the structured fields.

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?

Front-loaded with the action, then constraints, then permissions, then return value — no filler sentences. It is dense to the point of being a single crammed block, but every clause (threshold semantics, 403 behavior, role scope) earns its place.

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 3-parameter mutation tool with no output schema, it covers what the tool does, who may call it, what the failure mode is, and that it returns the saved settings. Nothing an agent needs to call it correctly is missing.

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 100%, so the schema already documents enabled, maxRating range and the projectId default/alias. The description restates the enabled requirement and the 1-5 threshold semantics but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('turn store reviews as reports on or off for one project and set the star threshold'), which cleanly separates it from read-side siblings like get_store_reviews, pull_store_reviews and run_store_review. The mutation intent and the two adjustable settings are clear from the first sentence.

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?

Explicitly names when it works and when it does not: an API key may turn intake off or change the threshold, but turning it on requires a signed-in owner/admin in the console and otherwise returns 403 HUMAN_REQUIRED. It also states the permission scope ('Project owners and admins only') and that projectId is optional, leaving little to inference.

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