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

With annotations already declaring readOnlyHint=false, destructiveHint=false, openWorldHint=false, and idempotentHint=false, the description adds genuinely non-obvious behavior: the deduplication of an already-queued run and the quota rule that only non-failing runs consume the monthly allowance. It does not cover permission requirements or what happens to a run that does fail, but the quota and dedupe disclosures are substantive.

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 tight sentences, each doing distinct work: purpose and return value first, then dedupe semantics, then quota cost. No filler and the most decision-relevant facts are 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?

For a mutation tool with no output schema, the description compensates well on the return side (run_id and status) and on the dedupe and cost semantics. However, it leaves all three inputs undocumented, including an 'attest' flag that plausibly changes what the run does, which is a real completeness gap given 0% schema coverage.

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% for three parameters, so the description carries the full burden and does not meet it. Only project_id is obliquely implied by 'on a connected project'; the meaning of 'label' and especially the 'attest' boolean is left entirely unexplained in both schema and description.

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 gives a specific verb and resource: 'Starts an authorization test run on a connected project', plus the immediate return value (run_id, status). That verb naturally separates it from the read-oriented siblings get_run_status and wait_for_run, but the description never names those siblings or states the distinction explicitly.

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 only implied: an agent can infer this is the entry point for kicking off a run, and the queued-run behavior tells it what happens on repeat calls. There is no explicit when-to-use vs. alternatives guidance (e.g., call this before wait_for_run, check list_projects first) and no stated prerequisites.

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