tickory_get_scan

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

No annotations are provided, and the description only says 'Fetch one scan by ID.' It does not disclose whether the operation is read-only, any authentication requirements, rate limits, or what happens if the scan does not exist. The description carries full burden for behavioral disclosure but fails to provide key details.

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, direct sentence with no extraneous words. It is front-loaded with the action and resource immediately, making it easy to scan.

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 presence of an output schema (not shown), the description does not need to explain return values. However, it could provide more context about the scan fields or usage scenarios. For a simple get operation, this is mostly complete but slightly lacking in context compared to the complexity of the tool set.

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 already describes the scan_id parameter as 'Scan identifier' with 100% coverage. The tool description adds 'by ID' which aligns but does not provide additional semantic value beyond the schema. Baseline score of 3 is appropriate.

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 'Fetch one scan by ID' clearly states the action (fetch), the resource (scan), and the identifier (by ID). It effectively distinguishes from sibling tools like tickory_list_scans which would retrieve multiple scans.

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 implies that this tool is for retrieving a single scan when the ID is known, but it does not explicitly state when to use it versus alternatives like tickory_list_scans or tickory_run_scan. No exclusions or alternative tool names are mentioned.

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