surety__post_bond

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

Discloses bond fee computation and freezing at post, and principal unit convention. However, with no annotations, description carries full burden; lacks information on side effects, authorization, or what happens after posting.

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?

Three sentences in a compact header format. Efficiently conveys key points, though the title-like prefix adds marginal value. No wasted sentences.

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?

With 5 parameters, no output schema, and no annotations, the description is incomplete. It covers only two parameters and omits return value, side effects, and full usage context.

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 coverage is 0%; description explains principal (minor units) and expires_at (ISO-8601) but completely omits coverage, currency, and principal_agent. Adds some meaning but leaves 3 params 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?

Description clearly states 'Post a surety bond behind an agent's promises' which is a specific verb-resource action. Distinguishes from siblings like activate, status, claim, etc. by the core action of posting.

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 guidance on when to use versus alternative tools (e.g., when to activate or release). Implies usage for initial bond posting but lacks specifics on prerequisites or contraindications.

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