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

Annotations indicate readOnly=false and idempotent=false, and the description substantially expands on this by explaining the two behavioral paths: internal jobs are applied end-to-end, while scraped jobs merely return an external URL and cannot be submitted by Remoet. It also discloses that duplicate applications are rejected, which is important side-effecting behavior beyond the annotation hints.

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?

The description is front-loaded with the primary purpose, then clearly separates behavior by job type, and ends with explicit safety constraints. It is long because the tool carries significant side effects and user-consent obligations, but every sentence adds necessary guidance and no content is wasted.

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 one simple parameter, no output schema, and a high-stakes side-effecting action, the description fully covers what the agent needs: input requirements, outcome differences, user-consent protocol, and failure conditions. Nothing necessary for correct invocation 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% and the single jobId parameter is already described as 'The ID of the job to apply to.' The description adds no additional parameter-level meaning, such as how to obtain the ID or any format caveats, so the baseline score of 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?

The description opens with a specific verb and resource: 'Apply to a job on behalf of the user, or get its application link.' It clearly distinguishes between internal and scraped job outcomes, which separates this tool from other job-related siblings like save_job or search_jobs.

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?

The description provides explicit usage guidance: confirm with the user before applying, review the job via search_jobs/get_starred_jobs/get_listing, cross-reference against the user's profile, flag skill gaps, and never apply without explicit consent. It also states constraints for internal jobs (must be published, not expired, no duplicates), giving clear when-to-use and when-not-to-use conditions.

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