search_find_orphan_devices

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

No annotations provided; description does not confirm read-only nature or other behaviors. For a simple list tool, minimal disclosure is acceptable but could mention it does not modify system state.

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?

One sentence of 12 words, front-loaded with verb, no extraneous information. Perfectly concise.

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 zero parameters and presence of output schema, description sufficiently covers tool's purpose. Could mention return fields or scope but overall adequate.

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?

Input schema has 0 parameters with 100% coverage. Baseline 4 applies; no parameter info needed. Description adds no extra parameter semantics but not required.

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?

Description clearly states it lists devices with no entities, using specific verb 'list' and resource 'orphan devices'. Distinguishes from sibling tools like search_search_devices by specifying the orphan condition.

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 explicit guidance on when to use vs alternatives. Sibling tools like search_find_unused_entities exist but no differentiation provided. Implied usage for finding orphan devices but lacks when-not or alternatives.

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