hcp_get_job

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral context by disclosing that prices are converted from cents to dollars, which affects how the agent should interpret the response. No contradiction with the annotations.

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 one tightly written sentence with no filler: it states the action, the resource, the key, and an important output detail. Every clause earns its place, and the primary purpose is front-loaded.

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-only getter with a full output schema, the description plus annotations are nearly complete. The only minor gap is not noting that the job_id typically comes from hcp_list_jobs, or behavior when the ID is not found, but these are not critical for correct invocation.

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 0%, so the description carries the burden. The phrase "by ID" clarifies that job_id is the unique selector for the job, adding slight meaning beyond the parameter name and type. However, it doesn't explain where to obtain the ID (e.g., from hcp_list_jobs) or any format expectations, making it minimally adequate for a single self-explanatory parameter.

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 and resource: "Get a single job by ID." This clearly distinguishes it from sibling list tools like hcp_list_jobs and hcp_get_customer, since it targets one job by its unique identifier. The additional note about price conversion is a useful extra detail.

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 intended use case is clear: when you need one specific job and know its ID. It doesn't explicitly mention alternatives or exclusions, but the precondition (having a job ID) is implicitly stated. The context is sufficient for an agent to know this tool is not for listing multiple jobs.

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