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

No annotations are provided, so the description carries the full burden. It does disclose a key behavioral trait: outcomes tied to a recorded routeId affect AgentRank and attribution. Yet it omits permissions, idempotency, consequences of repeated reporting, and what the response looks like, leaving substantial behavioral gaps.

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, front-loaded with the tool's purpose, and no redundant or filler content. The second sentence adds critical context about routeId significance without wasting words.

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 mutation tool with 6 parameters, no annotations, and no output schema, the description leaves too many gaps: parameter semantics, permissions, idempotency, and expected response are all absent. The AgentRank note is helpful but insufficient for this complexity.

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. The description implies the status values and stresses the importance of routeId, but it leaves providerId, value, summary, and currency completely unexplained and does not compensate for the lack of schema documentation.

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 uses a specific verb ('Report') and resource ('routed request outcome') and enumerates the three statuses (completed, failed, disputed). It clearly conveys the tool's function, though it does not explicitly differentiate from sibling tools such as ventru_create_route or ventru_build_action_capsule.

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?

The description implies usage after a route has been recorded ('Only outcomes tied to a recorded routeId') and explains the condition under which the report matters. However, it does not state when not to use this tool versus alternatives, nor does it name any sibling tool for comparison or exclusion.

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