Save or Skip Matches

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

Adds real behavior beyond annotations: skip reasons feed the matcher to improve future matches, and 'Nothing is sent to any employer and nothing is spent' addresses side-effect concerns that the idempotent/destructive hints don't cover. Doesn't note whether saved items can later be un-saved, but the persistence and feedback-loop semantics are well disclosed.

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?

Front-loaded with the core action, then constraints, side-effect guarantees, an exclusion, and a next step. The long reason list is dense but justified since it's the enum values. Slightly dense but every clause carries routing or behavior information.

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 an output schema exists, return values needn't be explained. The description covers the action semantics, side effects, source of ids, exclusions, and follow-up. For a 3-param mutation tool this is essentially complete; only a note on un-saving saved matches is missing.

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%, so baseline is 3. The description adds meaning: reason enum values are enumerated in prose and tied to the skip action, and job_match_ids is bounded at 25 and sourced from aiapplyd_get_matches in a way that exceeds the schema's bare description.

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?

States a specific verb pair (save/skip) on a specific resource (job matches) and frames the trigger question 'want this one?'. It distinguishes itself from siblings by naming aiapplyd_get_matches as the source and aiapplyd_apply as the different action.

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?

Explicit exclusions: 'Do not use it to apply; use aiapplyd_apply.' Explicit source: 'Pass up to 25 job_match_ids from aiapplyd_get_matches.' Explicit next step: 'Next: aiapplyd_get_matches for the next matches.' When-to-use and the alternative are both provided.

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