Find devices

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explicitly discloses the client-side filtering implementation, pagination behavior, case-insensitive substring matching, and platform coverage (macOS and iOS/iPadOS). This goes well beyond the schema and gives agents critical insight into how the tool operates.

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 two concise sentences with no filler. The first sentence states the core purpose and searchable fields, while the second adds essential implementation context about pagination and platform coverage. Every clause contributes meaning, and the key information is front-loaded.

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 simple search tool with two parameters, no output schema, and no annotations, the description provides all necessary context: what it searches, how matching works (case-insensitive substring), what platforms it covers, and its implementation behavior (client-side filtering). No critical information appears missing for an agent to select and invoke the tool correctly.

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 covers both parameters with descriptive text (100% coverage), so the baseline is 3. The description adds value by clarifying that 'serial' means serial number, 'id' means device id, 'user' means user id, and by stating the matching is case-insensitive—details not fully present in the schema. This enhances understanding beyond the structured definitions.

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 it searches the fleet by specific fields (serial number, device name, model, device id, or user id) with case-insensitive substring matching. This specific verb+resource combination distinguishes it from sibling find tools that target different resources, such as findOutdatedDevices or findDeviceGroups.

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 notes that it paginates and filters client-side due to no confirmed server-side filter, which implies performance considerations but does not explicitly state when to use this tool versus alternatives. No exclusions or alternative tool references are provided, so guidance is implied rather than explicit.

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