get_job

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

No annotations, but description adds HTTP mapping and tier hint '[tier: readonly-owner]' suggesting read-only behavior. Lacks details on error cases or authorization bounds.

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?

Three short sentences, but the second sentence 'Required on create: status by UUID' is ambiguous and dilutes clarity.

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?

Covers basic purpose and HTTP route, but with no output schema, annotations, or parameter descriptions, leaves gaps for a complete understanding.

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 has one parameter 'uuid' with no description. Description does not clarify what uuid represents (e.g., job UUID) beyond the tool name.

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?

Clearly states 'Get a single job (work order)' with verb and resource. Distinguishes from list_jobs by specifying single vs list. Also includes HTTP mapping.

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?

Implies usage for retrieving a single job after creation via the 'Required on create' note, but no explicit when-to-use or alternatives provided.

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