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

With no annotations supplied, the description carries the behavioral burden, and it does disclose the single most important trait: the tool is deprecated because the underlying manager settles payments at subscribe/renew time. It omits whether the call errors, returns empty, or silently succeeds — the practical behavior an agent needs before invoking.

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 front-loaded sentence beginning with 'Deprecated' — the most decision-relevant token comes first, and every clause earns its place by explaining the deprecation rationale. Nothing is padded or redundant.

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 deprecated two-parameter tool with full schema coverage and no output schema, the description covers the crucial 'why not to use it' but leaves two gaps an agent would want closed: what to use instead, and what a call actually returns or raises. Adequate but not fully self-sufficient.

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%: subscriptionId and the chain enum (bsc/ethereum/base, Sepolia unsupported) are fully documented in the schema. The description adds no parameter-level meaning, which is acceptable at this coverage level but leaves it at baseline.

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 tells the agent the tool is deprecated and explains why (the ERC8004SubscriptionManager settles on subscribe/renew, so no escrow exists), which implies the tool's nominal job is releasing subscription escrow. However, it never states positively what the tool does or did — the verb 'release' only appears in the resource name and in the negation 'no escrow to release' — so the operation itself is inferred rather than described.

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 deprecation notice strongly implies 'do not call this,' which is the essential usage guidance. It stops short of naming a replacement or sibling (e.g., actora_subscription_cancel or actora_subscription_detail) or saying whether invocation still succeeds as a no-op versus reverting, leaving the agent to guess the next step.

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