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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds what fields are returned (description, employment type, work locations), which is useful context beyond annotations, but doesn't mention errors, empty results, or rate limits.

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 tightly-written sentences; the primary capability and dependency are both front-loaded with no filler.

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?

Has output schema, so return-value explanation is not needed; description supplies the key workflow context (use board tool first). Minor gap: no mention of what happens when id is invalid or how large the returned description can be.

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 both parameters are documented ('Rippling job uuid', 'Rippling board slug'). The description echoes this by saying 'using its listing `id` and `company` board slug' but adds no syntax or format detail beyond schema. Baseline 3.

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?

Specific verb+resource: 'Fetch one Rippling job's full description, employment type, and work locations.' This clearly distinguishes it from the sibling board tool jobs_rippling_board and from other ATS job detail tools (jobs_greenhouse_job, jobs_lever_posting, etc.).

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 names jobs_rippling_board as the discovery mechanism, implying this tool is for retrieving a specific job once you have the id. No explicit exclusions or when-not-to-use, but the dependency (need company + id from board tool) is clear.

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