MCPAmpel

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 adds context that results are 'full detailed' (suggesting comprehensive data retrieval), but fails to disclose whether this is a read-only operation, if there are rate limits, or what happens if the scan is incomplete.

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 10-word sentence that front-loads the action ('Get') and immediately qualifies the scope. There is no redundant or wasted language.

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 the simple single-parameter schema and lack of output schema, the description is minimally adequate. However, it could improve by clarifying that this retrieves results from previously initiated scans (complementing the sibling scan tools) or hinting at the output structure since no output schema exists.

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 100% description coverage ('UUID of the scan'), establishing a baseline of 3. The description mentions 'by its ID' which aligns with the scan_id parameter, but adds no additional semantics regarding ID format, validation rules, or where to obtain the ID from sibling tools.

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 verb 'Get' and the resource 'full detailed results for a specific scan', distinguishing it from sibling tools like 'scan_my_servers' or 'scan_url' which likely initiate scans. However, it does not explicitly differentiate from 'check_status' (which might return metadata vs. full results) or explicitly state this is for retrieving completed scan data.

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 its siblings. It does not mention that this should be used after initiating a scan with 'scan_my_servers' or 'scan_url', nor when to prefer 'check_status' instead.

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