source_monitor_snapshot

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

Discloses side effect (writes to out_path). No annotations provided, so description carries burden. Missing details on overwrite behavior, permissions, or idempotency, which could affect agent decision-making.

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 short sentences plus a code-like instruction. No fluff, front-loaded with purpose. Every sentence adds value.

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?

Provides purpose, output, and follow-up step. Lacks minor behavioral details (e.g., file overwrite), but output schema exists to fill return value gaps. Adequate for a simple snapshot tool.

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 all 3 parameters with descriptions. The description adds context about 'keyless provider' and 'source_ids', but does not significantly extend schema info. Baseline 3 applies due to 100% 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?

Clear verb+resource+method: 'Take a snapshot of current job postings' and 'Writes a JSON file'. Distinguishes from sibling 'monitor_diff' which detects new postings.

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 suggests using 'monitor_diff' later, implying a sequencing step. Does not explicitly state when not to use, but provides clear context and alternative.

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