boond_accounts_search

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

No annotations are provided, so the description must carry the full burden. 'Search' implies a read-only operation, but the description does not disclose pagination behavior, result scope, authentication needs, or what data is returned. This is a significant gap for an unannotated 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?

The description is brief and contains no wasted words or repetition. It front-loads the core action and resource. However, it is so short that it sacrifices substantive guidance, so it is not a perfect conciseness score.

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 tool with three undocumented parameters, no annotations, and no output schema, the description is incomplete. An agent would not know what criteria are supported, how pagination works, what a successful response looks like, or how this search differs from sibling searches.

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 hints that the 'query' parameter accepts a username or criteria, but it does not explain query syntax, how 'criteria' are expressed, or what 'page' and 'limit' control. Two of the three parameters are effectively undocumented.

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 states a specific action ('search') and resource ('accounts'), and adds a concrete searchable field ('username'). It is clear enough, but 'criteria' is vague and it does not distinguish this from sibling search tools or from boond_accounts_get beyond the verb.

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 description gives no guidance on when to use this tool versus boond_accounts_get, boond_accounts_create, or the many other _search tools. There is no mention of prerequisites, typical use cases, or when a different tool would be more appropriate.

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