inkog_deep_scan

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

No annotations provided, so description carries full burden. Discloses scan duration (~10 minutes) and role requirement, but does not confirm read-only nature or potential side effects. While 'scan' implies non-destructive, explicit statement would improve transparency.

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?

Compact three-sentence description: purpose, capability, and key usage notes (role, duration). Front-loaded with core functionality, no redundant or filler content.

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?

Covers essential aspects for a scan tool: purpose, detection capability, prerequisites, and timely warning. Lacks mention of output format or result handling, but no output schema exists and siblings may follow common patterns.

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 100% with clear descriptions for both parameters (path and agent_name). The description adds no additional semantic meaning beyond the schema, meeting the baseline expectation for high 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?

Clearly states it performs a deep scan using advanced analysis to detect complex vulnerabilities and logic flaws, distinguishing from pattern-based scanning. Explicitly requires the Inkog Deep role, differentiating from sibling tools like inkog_scan.

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?

Provides context for when to use (for complex issues) and prerequisites (requires Inkog Deep role). Includes important temporal information (10 minutes) and user communication requirement. However, does not explicitly state when not to use or compare to alternatives like inkog_scan for faster results.

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