searchDevices

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 indicates a search operation but does not explicitly state if it is read-only, or describe behavior regarding empty results, pagination, or performance. The description is adequate but could add more behavioral context.

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?

Two concise sentences with no wasted words. The purpose and behavior are front-loaded. Every sentence adds value.

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?

The tool is simple (search by key, returns devices). The description adequately explains global scope. Without an output schema, it would be helpful to mention the structure of returned devices, but for a basic search tool, this is fairly complete.

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 schema has no descriptions (0% coverage). The description explains that 'searchKey' is the key to match, adding meaning. However, the 'customHeaders' parameter is not explained. The description partially compensates for low coverage but is not exhaustive.

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 clearly states the verb 'Search', the resource 'devices', and the scope 'globally across all sites'. It also indicates the output ('Returns devices matching the search key'). This distinguishes it from siblings like 'getDevice' (specific device) and 'listDevices' (likely lists all devices without 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?

The description provides clear context by specifying 'globally across all sites', implying it is for cross-site searching. However, it does not explicitly state when not to use this tool or mention alternatives, though the sibling list offers many specific getter tools.

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