scan_message

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

Description details that the tool returns a verdict, risk score, category, confidence, reasons flagged, and recommended actions. This goes beyond the tool name, and no annotations are provided, so the description carries the full burden. No contradictory or missing behavioral info.

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?

Description is concise and front-loaded with the primary action. Every sentence adds value without redundancy. No unnecessary words.

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 only two parameters and no nested objects or output schema, the description fully covers purpose, usage, parameters, and expected output. No gaps or missing information.

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%, but the description adds context by explaining that input can be SMS, email, etc., and clarifies source types. It also mentions minimum 8 characters, which is not in the schema's 'description' field.

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 the tool scans a suspicious message, URL, or text for scam indicators using ScamCheck AI, with specific verb 'scan' and resource 'suspicious content'. It distinguishes the tool's purpose well even without sibling context.

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 says 'Use this whenever a user shares a message they received and wants to know if it's a scam.' Provides clear context for when to use, though no exclusions or alternatives are mentioned.

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