scan_area

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'multiple snapshots' and 'systematically scan', implying a sequence of operations, but doesn't specify whether this is a read-only operation, if it affects system state, what the output format might be, or any performance considerations like time or resource usage.

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 a single, efficient sentence that gets straight to the point without unnecessary words. It's appropriately sized for a basic tool, though it could be more front-loaded with key distinctions.

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 tool with 2 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, how the scanning behavior works, or provide enough context for an agent to understand when and how to use it effectively compared to sibling tools.

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 input schema has 2 parameters with 0% description coverage, and the tool description provides no information about what 'pattern' or 'steps' mean in context. While 'pattern' has an enum, the description doesn't explain the semantic difference between 'horizontal', 'vertical', etc., or how 'steps' relates to the scanning process.

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 'Systematically scan area with multiple snapshots' states a general purpose (scanning with snapshots) but lacks specificity about what resource is being scanned or how this differs from sibling tools like 'take_snapshot' or 'look_and_analyze'. It uses a clear verb ('scan') but doesn't distinguish itself from alternatives.

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 no guidance on when to use this tool versus alternatives like 'take_snapshot' (single snapshot) or 'look_and_analyze' (analysis-focused). There's no mention of prerequisites, appropriate contexts, or exclusions, leaving the agent with no usage direction.

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