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

With no annotations, the description carries the behavioral disclosure burden. It does add useful information about credit charging and automatic refunds on failed verification/execution. However, it does not disclose other behavioral traits such as side effects, required permissions, or what a successful execution returns.

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?

The description is a single, front-loaded sentence that communicates the core purpose and a critical billing behavior without wasted words. It is concise and every clause adds value.

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?

Given six parameters, nested objects, no output schema, and no annotations, a one-sentence description is insufficient. The agent is left without enough guidance on how parameters relate to one another, what the execution produces, or how to sequence this with outcome_quote and outcome_verify.

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 only 33%, and the description does not compensate by explaining parameters like options, criteria, objective, or outcome_type. Only the schema's input and contract_id fields have any descriptive coverage; the remaining parameters are effectively undocumented.

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 states a specific action ('Execute a HumanMirror Outcome contract') with a clear resource, distinguishing it from quote/verify siblings. However, it does not explicitly contrast itself with outcome_verify or outcome_quote, so the differentiation is mostly implicit.

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 provides no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no explicit alternative routing. The only workflow hint comes from the schema's contract_id reference to outcome_quote, not from the description itself.

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