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

With no annotations, the description carries full burden. It implies a read-only list operation by stating it lists pricing, but does not explicitly declare it as non-destructive, nor does it disclose authentication needs, rate limits, or side effects. Adequate but not thorough.

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?

One concise sentence covering key points (free/pro/team pricing, payment method, agent payment). No fluff, but could be improved by adding structure or bullet points for clarity.

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 no output schema and no parameters, the description is reasonably complete. It explains the what and a notable detail (ETH on-chain, no Stripe). However, it lacks details on output format or any constraints, which are not critical but would enhance completeness.

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?

No parameters exist, and schema coverage is 100%, so the description adds no parameter info. Baseline is 4 per rubric; description appropriately omits param details.

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 tool lists Free/Pro/Team pricing and how agents pay for write tools. It uses specific verb 'List' and specifies the resource 'pricing', distinguishing it from siblings like stocktoken_subscription_tiers by mentioning payment details (ETH on-chain, no Stripe).

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 vs alternatives such as stocktoken_subscription_tiers or stocktoken_fees. The description does not mention prerequisites, context, or when not to use it, leaving the agent to infer usage without explicit direction.

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