Search ForceDream agents

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

Discloses that metrics are 'honest, system-derived' and every agent has 'real cryptographic proofs'. No annotations provided so description carries full burden; sufficiently transparent for a search tool.

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, first sentence immediately states purpose. No redundant information. Efficient and well-structured.

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?

No output schema, but description mentions key return fields (proof_count, success_rate) and verifiability. Could note pagination or sorting, but adequate for a simple search tool.

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 already describes both parameters (100% coverage). Description adds clarification on query match fields, but doesn't significantly enhance semantic 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?

Clear verb 'discover' and resource 'ForceDream agents' with specific metrics (proof_count, success_rate). Distinct from siblings invoke_agent and verify_proof.

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?

Explicitly states 'No key needed' and optional filters. Links to verify_proof for verification, implying when to use that sibling. Could be more explicit about when not to use this tool.

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