byte_unsubscribe

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

Describes effects (next block, no billing, no data flow) and reversibility (resubscribe via byte_subscribe). Adds substantial context beyond annotations, with no contradiction.

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?

Four concise, front-loaded sentences with no wasted words. Every sentence adds value.

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?

Simple tool with one parameter and output schema. Description covers usage context, prerequisites, effects, and reversibility. Fully complete for an agent to select and invoke correctly.

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?

Parameter 'publisher' already fully described in schema (address pattern). Description adds no new semantic details beyond what schema provides. With 100% coverage, baseline 3 applies.

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?

Clearly states 'Unsubscribe from a publisher's data feed', specifying the action and resource. Distinguishes from sibling tools like byte_subscribe and byte_subscription_health.

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?

Explicitly advises when to use (pivoted content or no longer want feed) and suggests checking byte_subscription_health first. Notes requirement for PRIVATE_KEY.

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