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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds useful negative scope — no plan display, no payment flow, no account mutation — which reinforces that this is a pure read with no side effects on billing.

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?

Two short sentences, purpose front-loaded, with the scope exclusions following immediately. Every clause carries information; nothing is padded.

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?

An output schema exists and the tool is parameterless, so the description does not need to explain return values. It covers purpose and boundaries adequately; the only minor gap is that it never explains what to do with a negative result (i.e., the fallback path when access is absent).

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?

The tool takes no parameters at all, so per the baseline there is nothing for the description to disambiguate. No parameter gaps exist to compensate for.

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 ('Check') and resource ('export access' for STL and 3MF) with a clear scope, so an agent knows exactly what question the tool answers. It does not, however, differentiate itself from the sibling export_design — it never says this is the entitlement check that precedes an actual export.

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?

The closing sentence bounds the tool by negation ('Does not display plans, initiate payment or modify account access'), which implies a pre-flight entitlement check, but it never states when to call it versus export_design or that it should be used before attempting an export. Usage is inferable rather than explicit.

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