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

Annotations already declare read-only, idempotent, and non-destructive, and the description adds meaningful guarantees beyond those: free, isolated, synthetic, and no production account, upload, payment, or private data. This is strong behavioral context for an agent deciding whether the tool is safe to invoke.

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 compact sentences with no filler. The primary action and safety qualifiers are front-loaded, and every clause adds useful information.

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 single-optional-parameter demo tool with annotations covering safety, the description provides sufficient context: purpose, safety, and scenario semantics. It could be slightly more explicit about what the demo returns or how results should be used, but the wording implies a behavior-comparison demonstration.

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 description coverage is 0%, so the description must compensate for the `scenario` parameter. It lists the exact enum values ('unchanged, one-partition-changed and missing-source') and explains them as behaviors to compare, adding semantic clarity the bare enum does not provide.

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 opens with a specific verb and object: 'Run a free isolated synthetic Reuse Autopilot demonstration.' It also names the three scenario behaviors, distinguishing this demo tool from the onboarding, assess, pricing, and security-profile siblings.

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 clearly states when to use the tool: before onboarding, as a free isolated synthetic trial with no production data. It does not explicitly name alternatives or exclusions, but the 'before onboarding' framing and safety guarantees make the intended context obvious.

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