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

With no annotations at all, the description carries the full burden of behavioral disclosure, and it does little with it. The word 'public' mildly signals a read-only, no-auth-required operation, but the description doesn't disclose failure modes (invalid id/slug), return format, missing-record behavior, or scope limits beyond 'public'.

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?

One 11-word sentence that front-loads the verb, resource, and the scoping qualifier 'public'. Every word carries meaning and nothing is redundant, achieving conciseness without under-specification.

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, read-style getter with no output schema, the description names what is returned ('details and description') and the schema fully specifies the input. The only notable gap is the workflow relationship to search_jobs, which is partially covered by the parameter description rather than the description itself.

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 description coverage is 100% and the single parameter idOrSlug is fully documented in the schema ('The job id or slug returned by search_jobs'), so the baseline of 3 applies. The description adds no parameter meaning beyond the schema, but none is needed given the schema's clarity.

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 states a specific verb+resource ('Get the public details and description of one Hidden Jobs offer'), clearly identifying this as a singular fetch operation. It is readily distinguishable from siblings like search_jobs (listing/search) and open_application_link (link opening), though it doesn't name them explicitly.

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 gives no guidance on when to use this tool versus search_jobs or open_application_link. The only usage hint lives in the schema parameter description ('returned by search_jobs'), which implies the search-then-fetch workflow, but the main description text itself provides no when-to-use context or exclusions.

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