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

Beyond the read-only annotations, the description discloses the paid x402 route, USDC pricing per credited creator, minimum and maximum cost, invoice behavior, and that an unpaid call returns payment requirements instead of data. These are important behavioral details an agent needs before invoking the tool.

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 front-loaded with purpose and return fields, but the payment terms are repeated several times, including the one-cent minimum and exact invoice amount. It is informative but not as tight as it could be.

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?

With no output schema, the description still explains the return shape well enough: metadata fields, preview clip availability, label/owner block, post-count attribution, and ownership crediting rules. It also covers payment behavior and unpaid-call behavior completely.

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 already 100%, so the baseline is 3, but the description adds useful meaning: q is described as title/artist search and pagination is tied to cost because limit determines how many creators are credited and billed. This goes beyond the schema without fully duplicating it.

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 states a specific resource and what it returns: music/audio metadata with title, artist, ISRC, artwork, and preview clips. It also distinguishes recordings from posts by saying credit belongs to the owning artist, never to accounts whose posts used the recording, which helps separate it from public_posts.

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 description gives clear context for searching by title or artist and pagination, but it does not explicitly say when to use this tool versus creator_listings, creator_profile, or public_posts. Usage is implied by the metadata focus rather than stated as routing guidance.

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