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

Discloses behavior beyond annotations: expired and withdrawn postings are not served, non-live ids return an error result, and read-only/free/attribution requirements are stated. It also mentions the source-permission caveat and the verification method for lastVerifiedAt.

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 action and object, and every clause carries needed caveats or payload fields. It is dense but not padded, and the length is justified by the absence of an output schema.

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?

For a one-parameter getter with no output schema, the description covers the return payload fields, error behavior for non-live ids, and attribution location. No significant gap remains for invocation or result interpretation.

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?

The input schema covers 100% of parameter semantics via the id description ('job_<slug>', bare slug also accepted). The description only restates that the id selects one posting and adds no syntax or format detail beyond the schema.

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 ('Fetch') and resource ('ONE nomado24 job posting by id') and enumerates what the complete v2 payload contains. The by-id retrieval is clearly distinct from search_jobs and get_job_statistics.

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 implies the tool is for retrieving a single known posting rather than searching or fetching statistics, and the schema notes ids come from search_jobs. It does not explicitly name sibling alternatives or exclusion conditions, so it is clear but not fully explicit.

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