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

Annotations already declare a safe read (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: handoff guidance is not authorization, the tool performs no browser/login/material actions, and it never accepts passwords, cookies, or tokens. It also tells the agent to inspect scope/period differences and re-verification needs in the result.

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?

Purpose is front-loaded in the first sentence, followed by safety and parameter guidance in a logical order. Several sentences are caveats, but each carries distinct information (authorization, secrets, fallback); it is dense without being bloated.

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 two-parameter read with no output schema, the description covers purpose, permission model, parameter usage, and what to read from the response. Return structure itself is not described, which is acceptable given no output schema exists, but a hint about the response shape would fully close the gap.

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 0%, so the description must carry the burden and it does: id is the site identifier, and materialId omitted returns everything while a materialId obtained from a prior response narrows to one material. That explains both parameters' meaning and even their acquisition flow, well beyond the raw pattern constraint.

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: checking login/paid-subscription conditions per material for a site ID. The scope is concrete enough to distinguish it from data-fetching siblings like get_site_details or get_research_pack, though it never names a sibling 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?

Gives real conditional guidance: members should follow memberHandoff and work in the owner-approved browser, and if permission is absent they should fall back to a verified public alternative. It also sets a clear negative boundary (no browser connection, login, or material lookup), but does not explicitly route against a named alternative tool.

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