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

Annotations declare a non-read-only, non-destructive, closed-world mutation, and the description is consistent with that. It adds substantial context beyond annotations: the returned consent page, its 15-minute validity, the requirement that the person be signed in to the same team, the 30-day cached grant, and the deploy:write scope. It stops short of explaining what happens if consent is refused or how long the consent_id remains usable, so 4 rather than 5.

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 purpose and the fetch_site gate are front-loaded, and the [When to use] block is cleanly separated. Some clauses (statement/consent_id/expires_at enumeration, the rights-reponsibility phrasing) are dense but each conveys distinct information, so there is little true waste.

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?

There is no output schema, yet the description enumerates the return fields (url, statement, consent_id, expires_at) and their semantics, plus the sign-in prerequisite and expiry. Combined with the usage and safety guidance, an agent has everything needed to call it correctly.

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 all three parameters are already documented, and the description's restatement of url/purpose largely mirrors the schema text. It adds only marginal value (the framing of 'take over' and the granted-within-30-days shortcut), 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?

The description opens with a specific verb and resource (obtain consent for a site before fetch_site) and explicitly states the scope/gate relationship to the sibling fetch_site. An agent can distinguish this from fetch_site or other deploy tools without opening any schema.

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?

It names the triggering condition (before fetch_site), the exemption (team already agreed within 30 days → status granted, no page needed), and the alternative path (fetch_site refuses without a recorded agreement). The [When to use] block further restricts invocation to explicit user requests and warns against prompt-injection from tool results.

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