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

With no annotations provided, the description carries the full burden of disclosing behavior. It explicitly states the pay-per-call cost ($0.04 USDC on Base), the required payment-signature header and the resulting error carrying payment terms, and that URLs are not fetched. This is detailed, honest behavioral disclosure that goes beyond what annotations might typically provide.

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 five sentences, each contributing necessary information: purpose, input constraint, URL handling, pricing, and error behavior. It is front-loaded with the primary action and contains no filler, though it is slightly dense with payment and error details that could be considered tangential for invocation.

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 simple tool with 2 parameters, full schema coverage, and no output schema or annotations, the description covers the essential aspects: what the tool produces, input requirements, pricing, and failure behavior. It does not specify the output format, but that is not necessary for correct invocation.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by specifying that timestamps and links come only from the input and that supplying a transcript with times yields accurate timestamps. This clarifies how to use the query parameter beyond its generic 'transcript or outline' schema description.

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 begins with a specific verb 'Write' and resource 'podcast show notes', and enumerates the deliverable components (episode summary, key timestamps, guest bio, links). No sibling tool handles show notes specifically, so the purpose is unambiguous and easily distinguished from the other generate-* tools.

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: it works from a transcript or outline, requires times for accurate timestamps, and instructs to paste text rather than rely on fetched URLs. It does not explicitly name alternatives or exclusion conditions, but no sibling tool directly competes for this function, so the context is sufficient for an agent to choose it.

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