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

Adds substantial context beyond annotations: requires connected Phorme account with training:write permission and a membership including programs; returns a link; failure mode when membership is missing; no purchase is initiated; idempotency semantics with idempotency_key. Annotations declare idempotentHint=true, and the description explains how to achieve it. No contradictions.

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?

Front-loads the trigger condition, then lists requirements, failure mode, exclusions, and idempotency. Six sentences with minimal waste, though slightly verbose for a three-parameter tool. Every sentence adds value but could be tightened.

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?

Complete for a write tool: covers preconditions, permissions, failure behavior, exclusions, and idempotency. Output schema exists, so return values need not be explained, though the description mentions returning a link. No gaps for an agent deciding whether and how to call it.

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 baseline is 3. Description adds meaning: preview_id refers to the preview being saved, idempotency_key reuse prevents duplicate copies, and confirmation must only be set after clear user confirmation. Slightly above baseline due to the idempotency explanation, though it largely aligns with schema descriptions.

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?

States a specific verb (save) and resource (program preview) with explicit scope: saves a preview to the connected Phorme account as a private program. Clearly distinguishes from sibling save_program_to_my_coaching_brain and save_workout_to_phorme by naming the destination and the source object.

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?

Explicit precondition: 'when the user has seen a program preview and clearly said to save it.' Also states what happens if prerequisites fail ('says so and saves nothing') and an explicit exclusion ('never starts a purchase'). This covers when-to-use, failure behavior, and a boundary condition.

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