boond_documents_search

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

No annotations are provided, so the description carries the full burden. It only says 'Search documents by criteria' and does not disclose whether query is full-text, whether query is required, how pagination behaves, what response shape to expect, or any other side effects or limits.

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 short and has no redundant wording, but it is under-specified rather than appropriately concise. It fails to include even minimal operational detail that would justify its brevity.

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 no annotations, no output schema, and 0% parameter coverage, this description leaves the agent almost entirely uninformed. For a search tool that takes three parameters and returns multiple documents, the description is far too thin to support correct invocation.

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%, so the description must compensate. It does not. The word 'criteria' hints at the query parameter but says nothing about page and limit, how criteria map to fields, or how query interacts with pagination. An agent would be guessing at argument semantics.

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 uses a direct verb and resource ('Search documents') and, given the sibling tools boond_documents_get/update/download, it is clear this is the list/find operation. The phrase 'by criteria' is vague about what criteria are supported, but it does distinguish search from the other document operations.

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?

There is no guidance on when to use this tool versus boond_documents_get or the many other *_search tools. The name suggests 'use this to search documents,' but no context, exclusions, or alternative routing is provided.

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