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

With no annotations, "Check" is the only indication that this is a non-mutating read operation. The description does not clarify whether the result is a boolean or richer status object, how inactive or nonexistent subscriptions are reported, or any authentication and failure behavior.

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?

A single short, front-loaded sentence states the operation and its two key scopes without filler. Its brevity is appropriate; the missing sibling distinction is a completeness issue rather than a structural one.

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?

The fully documented input schema makes the three arguments straightforward to supply, and the operation itself is simple. However, with no output schema or annotations, the result contract and read behavior remain implicit, while the central-versus-noncentral subscription-check distinction is unresolved.

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%, including the chain enum, default, and Sepolia exclusion, so the baseline score applies. The description's references to a wallet and agent add no syntax, format, or chain-selection detail beyond the documented subscriberAddress, agentId, and chain parameters.

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 specifies the operation ("Check"), resource ("active subscription"), and scope (a wallet for an agent), making the basic function clear. It does not distinguish this tool from actora_central_subscription_check or related subscription-detail tools.

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 wording implies a point-in-time subscription-status lookup, providing minimal usage context. There is no explicit when-to-use or when-not-to-use guidance, prerequisite, or alternative, particularly for choosing between this tool and actora_central_subscription_check or actora_subscription_detail.

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