ecash_find_agents

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

No annotations are provided, so the description must fully disclose behavioral traits. The verb 'Find' implies a read-only operation, but the description does not state any side effects, access requirements, result ordering, or behavior when no filters are applied. This leaves the agent guessing about important execution semantics.

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 two short sentences, front-loaded with the core purpose. Every word earns its place—no fluff, no repetition. It efficiently conveys the main function and the primary use case.

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 relatively simple search tool with no output schema and no annotations, the description covers the essential purpose and a valid use case. However, it omits details like what the response contains, whether results are paginated (despite the 'limit' parameter), and how 'registered' is defined. This is acceptable for a minimal viable description but not comprehensive.

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?

The input schema provides 100% coverage with descriptions for all three parameters, so the baseline is 3. The description adds some alignment by naming 'skill' and 'minimum tier', but does not add deeper semantics beyond what the schema already specifies. The 'limit' parameter is not mentioned, but its purpose is clear from the 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 opens with a specific verb ('Find') and a clear resource ('registered agents') scoped by 'skill and minimum tier'. This clearly distinguishes it from sibling tools like ecash_get_agent or ecash_get_agent_info, which likely retrieve individual agents rather than search across them.

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?

The second sentence 'Useful for discovering agents that can complete specific tasks' provides clear context for when to use this tool. It does not explicitly mention alternatives or when not to use it, but the stated use case is unambiguous and differentiates from the other ecash tools.

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