what-is-ap2

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

No annotations exist, so the description carries the burden. It discloses the lesson topic and content scope, but does not explicitly state that this is a read-only informational tool or describe what the user will see/experience. The 'skip' condition adds behavioral context, but it's more usage guidance than transparency about tool behavior.

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 focused sentences: the first identifies the lesson and provides a precise definition, the second offers a practical skip condition. Every word earns its place with no redundancy.

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 informational lesson with no parameters or output schema, the description gives sufficient context: what the lesson covers, how it relates to x402, and who should skip it. It could be slightly more explicit about expected output, but the simplicity of the tool makes this adequate.

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?

The tool has zero parameters, so the baseline is 4. The description adds useful context about the subject matter and a conditional for usage, which enriches the tool's meaning beyond the empty schema.

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 this is Lesson 13 about AP2 (Agent Payments Protocol), explicitly defining it as the trust/authorization layer above x402 for delegated payments. This distinguishes it from sibling lessons like what-is-x402 and conveys a specific educational resource.

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?

It provides an explicit exclusion ('Skip if you're spending your own funds'), implying use when delegated payments are involved. While it doesn't name alternative tools directly, the contrast with x402 and the skip condition offer practical guidance.

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