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

With no annotations, the description must fully convey behavior. It implies a read-only on-chain query but does not disclose potential side effects (likely none), authentication requirements, rate limits, or failure modes. The deployment note is parametric, not behavioral.

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 description is a single sentence with no redundancy. However, it could convey more information without becoming verbose, such as clarifying the parameter or return value. It earns a high score for conciseness but not perfect due to missing context.

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 one parameter and no output schema, the description should explain what 'subscription status' entails, what the returned data looks like, and how the owner parameter is interpreted. The current text is too brief to be fully actionable for an agent.

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%, and the description adds no meaning to the sole parameter 'owner'. It does not specify what the owner represents (wallet address?), its format, or constraints beyond the schema's type string. This is a critical gap.

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 action ('Check on-chain subscription status') and the resource ('for a wallet'). The name 'subscription_status' aligns with this purpose. However, it does not explicitly differentiate from sibling tools like 'stocktoken_subscription_tiers' or 'stocktoken_subscribe_plan', though the verb 'check' implies a read operation.

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?

No guidance on when to use this tool versus alternatives, prerequisites, or exclusions. The parenthetical about SUBSCRIPTION_REGISTRY_ADDRESS is a deployment constraint, not usage guidance. A clearer usage context would improve the score.

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