rh_estimate_price

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

With no annotations, the description carries the full behavioral burden. It discloses one useful trait — the result is an estimate, not official pricing — but says nothing about auth requirements, rate limits, what the nested payload must contain, or what the response 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?

Two short, front-loaded sentences with no filler; the core action leads. The brevity comes at the cost of substance, but structurally it is efficient.

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 tool with an undocumented nested payload object and no output schema, the definition is too thin — it omits what to pass for 'endpoint' and 'payload' and what the estimate result looks like, so an agent cannot call it 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% for two parameters, one of which is a free-form nested object with additionalProperties. The description adds no meaning about 'endpoint' or 'payload' structure, leaving both entirely opaque to the agent.

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 verb (Estimate) and resource (a public catalog price), which distinguishes it from the workflow/model siblings. It is clear what the tool does at a high level, though it never explains what the cryptic 'endpoint' identifier refers to.

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?

'Verify official RunningHub pricing before showing a final cost' implies a usage context (pre-flight cost estimation, not authoritative), which is helpful. However, it names no alternatives and gives no explicit when-to-use/when-not conditions relative to the many sibling tools.

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