localsend_scan

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

No annotations provided; description mentions return values but does not disclose network behavior (e.g., uses UDP broadcast), permissions, or side effects. Adequate but not fully transparent.

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, front-loaded with action and result. No wasted 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?

For a simple scan tool with one optional parameter and no output schema, the description lists return fields. Minor gap: does not specify that returns a list of devices. Still mostly 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?

Only one parameter (timeout) with full schema description ('Scan duration in seconds'). Description does not add extra meaning beyond schema. Baseline score of 3 due to 100% 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 clearly states the tool scans LAN for LocalSend receivers and returns specific details (aliases, IPs, ports, protocols). This distinguishes it from the sibling tool 'localsend_send' which sends files.

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?

Usage is implied (scan before sending), but no explicit guidance on when to use this vs. the sibling tool. No exclusions or prerequisites mentioned.

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