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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description adds useful context such as sandbox/demo status, credential requirements, and JSON error surfacing, but internal contradictions ('prepares a template' vs 'Records the operating terms') and heavy legal boilerplate reduce reliability.

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 bloated with defensive boilerplate and front-loads 'Unavailable historical backend' rather than the tool's purpose. The core action is split across contradictory sentences, so the structure is poor and fails to front-load what an agent needs to invoke the tool correctly.

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 an open-world, non-idempotent, potentially destructive proxy tool with no output schema, the description leaves key gaps: it does not explain the sole 'mode' parameter, does not clarify return behavior, and its conflicting statements make the operating boundary unclear.

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% for the sole parameter 'mode', and the description never mentions mode or its semantics. It only vaguely refers to 'supplied values or defaults' and lists operating fields, so it does not compensate for the schema gap.

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 identifies a specific resource (SLA policy template / operating terms for a rail run) and action (prepares/create/records), but multiple conflicting framings ('sandbox/demo template', 'Create an operational promise', 'Records the operating terms') make it hard to state in one sentence what the tool actually does. It also does not distinguish this tool from siblings like wever_agent-work-order-rail or wever_agent-decision-packet-rail.

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?

No explicit when-to-use, when-not-to-use, or alternative tool guidance is provided. The mention of required credentials and backend status is contextual information, not usage guidance that helps an agent decide between this tool and its many siblings.

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