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

Beyond the annotations (readOnly=false, destructive=false), it discloses that effect is immediate at the URL, that machine reconfiguration happens in the background within seconds, that a sleeping project is woken, that an in-progress deploy picks the change up on completion, that same-value calls are no-ops, and that the share URL is stable. It also flags a side effect an agent must relay: a warning when a restricted project has a public bucket.

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 core operation is front-loaded in the first clause and every subsequent sentence carries real behavioral information. The parenthetical-heavy run-on styling (three nested asides in one sentence) slightly hurts scannability and could be split for faster parsing.

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 an output schema and annotations already covering safety and return shape, the description fills the remaining gaps an agent needs: timing, edge cases (sleeping project, in-flight deploy, no-op), URL stability, and the bucket/app scope boundary. Nothing material is left unspecified.

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%, so the baseline is 3, but the description goes further by explaining what 'restricted' operationally means (owner plus shared emails, verified by a one-time code) rather than merely restating the enum. project_id receives no extra treatment, but nothing is ambiguous.

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+resource ('flip a spawnpoint project between restricted ... and public') and immediately defines both states, so an agent knows exactly what changes. It is distinguishable from set_storage_visibility/add_storage because it explicitly scopes the gate to the app rather than a bucket.

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?

Usage is implied: call this to change app access at the share URL, and the description contrasts the app gate with a public bucket. However, it never names the sibling tools an agent might confuse it with (share_project, unshare_project, set_storage_visibility, set_share_slug) or states when not to use it, so routing still requires inference.

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