find_accounts

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

With no annotations, the description bears full burden for behavioral disclosure. It only states 'search', implying a safe read operation, but fails to mention pagination, sorting, filtering behavior, authentication needs, or any side effects. The presence of 'top', 'skip', 'orderby', and 'odata_filter' parameters suggests complex querying not explained.

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 a single efficient sentence, well front-loaded with the core action. However, it lacks any structural elements (bullets, sections) that could convey more information without adding length.

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 the tool has 6 parameters, no schema descriptions, and a likely complex output schema, the description is woefully incomplete. It does not explain pagination, advanced filtering, ordering, or how results are returned. A user would need external documentation to use the tool effectively.

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 adds meaning for 'name' and 'email' (searchable fields), but ignores 'top', 'skip', 'orderby', and 'odata_filter' parameters entirely. This leaves the majority of parameters unexplained.

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 explicitly states the verb 'search' and the resource 'client accounts', and specifies the search criteria 'by name or email'. This clearly distinguishes it from sibling find tools targeting other entities.

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 provides no guidance on when to use this tool versus alternatives like 'get_account' (for a single account) or other find tools. No context about typical use cases or limitations is given.

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