scan_first

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

No annotations provided, so description must disclose all behavioral traits. It states it returns match count and mentions the scan types, but does not disclose whether it modifies state, if the process must be attached, or what happens if parameters are invalid. Missing explicit read-only or side-effect information.

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?

Very concise: three sentences covering purpose, scan types, and follow-up steps. Front-loaded with main action, then details. No redundant phrasing.

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 7 parameters, no output schema, and no annotations, the description is incomplete. Missing explanation of parameters like start/stop (address range), value/value2 format, value_type, only_one. Does not describe return format beyond 'match count'.

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%, yet description only explains scan_type and partially value2 (needed for 'between'). Other parameters (start, stop, value, value2 generally, only_one, value_type) are not described. Description adds limited value beyond schema.

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 'Run a first scan over the attached process and return the match count', using specific verb 'run a first scan' and resource 'attached process'. It distinguishes from siblings like scan_next (narrowing) and scan_results (paging).

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?

Explicitly mentions when to use this tool (first scan) and directs to scan_next and scan_results for follow-up. Explains scan_type options and gives specific guidance for 'unknown' and 'between'. Lacks explicit when-not-to-use but context is clear.

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