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

Beyond the readOnly/idempotent annotations, it discloses the absence of a subscription store, explains why the answer is 'no subscription' rather than a fabricated empty record, and names the reasons the lane is not live. This is substantial added behavioral context that helps an agent trust and interpret 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?

It is front-loaded with the core purpose, but the latter half contains expansive philosophical/economic phrasing ('It buys no token. It promises no return...') that is arguably more than a tool description needs. Acceptable but not tight.

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?

Given a single well-documented parameter, rich annotations, and an output schema, the description supplies the important non-obvious context: the honest no-subscription answer, the place-owned nature of standing, and the absence of payment expectations. Nothing critical for invoking the tool appears missing.

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 schema already covers the only parameter (wallet, with format 0x... and public-read caveat), so the description carries no additional parameter detail. Baseline 3 applies due to high schema coverage.

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 clearly states the operation: given a wallet, return its regenerative provisioning subscription state, with the key twist that the state is honestly reported as absent ('no subscription'). It does not explicitly compare itself to sibling tools like regen_provisioning_subscription_quote or place_standing, so it stops short of 5 on the rubric's sibling-differentiation requirement.

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 gives useful context around expectations (free, keyless, buys no token, promises no return) and points to GET /labor/standing?place= for place standing, but it never says concretely when to prefer this tool over its siblings or under what conditions to use an alternative. The guidance is implied rather than explicit.

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