qbo_employees_search

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

No annotations provided; description only states search method. Lacks disclosure of behavior such as case sensitivity, sorting, error handling, or performance implications. The LIKE match detail is helpful but insufficient for full transparency.

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?

Single sentence, well-structured, front-loaded with key information. No unnecessary words.

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?

Minimal description for a simple search tool. No output schema, so description should explain return values or pagination. While adequate for basic understanding, lacks details about result format and error conditions.

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 coverage is 100% with clear parameter descriptions. The description adds 'Employee records' context and confirms LIKE match on DisplayName, but this largely repeats schema info. Baseline 3 is appropriate given high schema coverage.

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 specific verb 'Search', identifies resource 'Employee records', and specifies method 'LIKE match' with field 'DisplayName'. This clearly distinguishes it from sibling tools like qbo_accounts_search or qbo_bills_search.

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?

No guidance on when to use this tool vs alternatives (e.g., qbo_employees_list, qbo_employees_get). Does not mention when not to use it or any prerequisites.

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