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

With no annotations, the description carries the full burden. It usefully discloses that a routeId is returned and that outcomes should be reported via ventru_report_outcome, but it omits whether recording a route creates any commitment, whether it is idempotent, and what permissions the user_approved mode requires.

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 tight sentences with the core action and the return value front-loaded. No filler, every clause carries 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 6-parameter creation tool with no annotations and no output schema, the description is far too thin: parameter meaning, preconditions, and side effects are all missing. An agent cannot reliably invoke this correctly from the description alone.

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% across 6 parameters, so the description must compensate. Only the authorization parameter is loosely echoed via the "quote-only or user-approved" phrasing; providerId, offerId, intent, capsuleId, and agent are left entirely unexplained.

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?

Names a specific verb and resource ("Record a ... route to a provider offer") and clarifies the two authorization modes. It does not explicitly distinguish itself from sibling tools beyond the mention of ventru_report_outcome, so it falls short of the top mark.

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?

Implies usage through "quote-only or user-approved" and redirects follow-up reporting to ventru_report_outcome. However it never states when an agent should create a route versus using ventru_find, ventru_search_providers, or ventru_build_action_capsule first, and no exclusions or prerequisites are given.

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