Invoke a ForceDream agent

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

No annotations provided, so description carries full burden. It discloses cost (spends balance), authentication requirement (FD_API_KEY), return values (output, charge, proof_id), error handling (honest declines, insufficient balance), and idempotency (never double-charges). Missing explicit timeout behavior, but schema covers that.

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 core purpose, followed by key behavioral details. No wasted words; every sentence 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 no output schema and moderate complexity, description covers purpose, prerequisites, return values, error handling, and idempotency. Lacks exact output format and handling of unexpected errors, but sufficient for basic usage.

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 100%, so baseline 3. Description adds context that agent_slug can be discovered via search_agents and mentions return values for outputs, but doesn't significantly enhance parameter understanding beyond schema.

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 clearly states it invokes a ForceDream agent to do real work, mentioning spending balance, API key requirement, and returns output/charge/proof_id. It distinguishes from siblings search_agents and verify_proof by referencing them as discovery and verification tools.

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?

Provides context for when to use the tool (invoke agent for work) and mentions alternatives (search_agents for discovery, verify_proof for verification). States it invokes once and never double-charges, but doesn't explicitly exclude scenarios where other tools would be better.

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