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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no note that the id comes from a board listing, no indication of auth requirements, freshness, or what 'full detail' includes versus the board entry.

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?

It is a single front-loaded fragment with no wasted words, which is good for brevity, but the terseness is under-specification rather than economy given a 2-param tool with no other documentation.

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?

An output schema exists, so return values need not be described. However, for a detail-fetch tool whose inputs are entirely undocumented, the description should at minimum explain how to obtain id/domain and how it relates to jobs_phenom_board; it does neither.

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 0% and both parameters (id, domain) are required, so the description carries the full burden. It says nothing about the identifier format or what 'domain' means (e.g. the company's Phenom-hosted careers domain), leaving both parameters semantically opaque.

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 phrase 'Single Phenom People job with full detail' names a specific resource and scope, and the word 'single' implicitly distinguishes it from the sibling jobs_phenom_board listing tool. It lacks an explicit verb (retrieve/fetch), but an agent can still tell what it returns without opening the schema.

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?

There is no when-to-use guidance, no mention of jobs_phenom_board as the source of the required id, and no statement of prerequisites. The agent must infer that this is the follow-up call to a board listing.

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