quick_scan

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

Discloses key behavioral traits: instant response time (5-10 seconds), read-only nature (consistent with readOnlyHint), and types of analysis performed. Adds meaningful context beyond annotations.

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?

Two concise sentences with no fluff. Front-loads the key value proposition ('INSTANT') and quickly explains what it does and when to use it. Every sentence earns its place.

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 purposes, usage guidelines, and output expectations (risk assessment, classification, concerns, key terms). Lacks details on output format or error conditions, but given low complexity and no output schema, it's nearly complete.

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 covers 100% of parameters with descriptions. The tool description adds no additional semantic detail about how parameters like fileName or perspective affect the analysis, so baseline 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?

Clearly states it provides instant contract analysis (5-10 seconds) with specific outputs like risk assessment, classification, and key terms. Differentiates from full analysis by emphasizing speed and initial triage.

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 advises using this tool FIRST before deciding if a full analysis is needed, and positions it for initial triage or quick questions. This guides appropriate usage and distinguishes from slower alternatives.

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