bluetooth_scan

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

With no annotations, description must disclose all behavioral traits. It states scanning duration but does not mention whether this is read-only, what happens to existing data, or if it requires pairing. Minimal disclosure.

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, no wasted words. Front-loaded with action and scope. Highly 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?

For a simple tool with an output schema (not shown) and one optional parameter, description covers the basic function. But missing parameter explanation and behavioral details reduce completeness.

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 0%, so description should explain the 'seconds' parameter. It does not, leaving the agent to infer meaning from default/title alone, which is insufficient.

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 tool scans for nearby Bluetooth devices, using specific verb and resource. However, it does not distinguish from sibling tools like bluetooth_devices or bluetooth_status, which have overlapping functionality.

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 scan vs other Bluetooth tools. Lacks context about prerequisites, alternatives, or exclusions. Only mentions duration implicitly.

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