what-is-ap2

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

With no annotations, the description transparently indicates this is an educational lesson, not an action tool. It explains what AP2 is and the context, adding behavioral context beyond the empty schema.

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?

Two sentences with no wasted words. The first sentence establishes curriculum position, the second defines AP2 and gives usage guidance. Front-loaded and efficient.

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 sufficient for a lesson tool. It explains what AP2 is and when to skip, but could elaborate on the lesson's content. Still, it adequately covers the essentials.

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, so baseline is 4. The description adds meaning about the tool's content and purpose, which is valuable given the lack of parameters.

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 is Lesson 13, defines AP2 as the trust/authorization layer above x402 for delegated payments, and includes a skip condition. This distinguishes it from sibling tools like 'what-is-x402'.

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?

Provides explicit guidance with 'Skip if you're spending your own funds,' indicating when not to use. Implicitly suggests use for delegated payments, though no direct alternatives are named.

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