get_print_job

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

Annotations already mark it as readOnlyHint: true and destructiveHint: false, so the description adds no additional behavioral context beyond those. The description does not mention any edge cases or constraints on the jobId parameter.

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 a single sentence with 15 words, efficiently conveying the purpose and what information is returned. No extraneous information.

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?

The tool has a simple fetch-by-ID interface with one parameter and no output schema. The description adequately states what is returned, but for a single-job retrieval, it is minimal and sufficient.

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%: the only parameter jobId is documented in the schema with type and minimum. The description does not add further meaning beyond the schema's own description.

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 clearly states this tool returns details for a specific print job by ID, listing the key fields included. It is distinct from siblings like list_print_jobs which lists jobs without details, and create_print_job which creates a new job.

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 that this is a lookup tool for a single job by ID, which contrasts with list_print_jobs for listing. However, it does not explicitly state when to use this vs alternatives or any prerequisites.

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