check_scam_patterns

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

Description adds 'offline, no key' and implies deterministic operation, complementing annotations (readOnlyHint, openWorldHint, idempotentHint). No contradictions.

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 sentences plus a use-when line; every sentence is informative. Extremely concise with no wasted 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?

Tool is simple (1 required param), schema and description fully cover purpose, usage, and parameters. Output schema exists (not shown but indicated). Complete guidance.

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?

Input schema already describes parameters (text, response_format) well. Description adds value by listing the specific scam patterns checked, providing context beyond schema.

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 'Scan message text for known recruiter/job-scam tactics', listing specific tactics. It distinguishes from sibling check_* tools by focusing on scam patterns in text.

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 states 'Use when: you have the raw offer text and want deterministic TTP hits.', providing clear condition for use.

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