apply_send_approved

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

No annotations provided, but description fully discloses safety rules enforced in code: only approved items processed, stops on payment URL, login context, sensitive fields, and dry-run behavior by default. Very transparent.

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?

Concise with two main parts: purpose and safety rules in bullet points. No wasted text, clear structure.

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?

Output schema exists, so return values are covered. Description covers purpose, usage, safety, and params. Complete for the tool's complexity (2 params, no enums, no nested objects).

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% (both parameters described). Description adds minimal extra meaning: queue_path as absolute path, confirm_send as dry-run vs submit. 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 the tool submits ATS applications for approved queue items via Chrome. Distinguishes from sibling tools like apply_queue_approve.

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?

Safety rules explicitly list when items are stopped (not approved, payment URL, login context, sensitive field). Explains confirm_send parameter for dry-run vs submission. No direct comparison to alternatives but clear context within ATS pipeline.

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