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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description adds useful context — that the response is a rich per-job dossier including overtime rule, timecard method, and workers' comp burden — but says nothing about auth requirements, rate limits, or behavior for an unknown job_id.

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?

Two compact clauses front-load the entity definition and then the field inventory; nothing is redundant. The field enumeration is long but each item conveys real response content that has no output schema to carry it.

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?

With no output schema, the enumerated field list is doing important work in telling the agent what a successful read returns, and annotations cover the safety profile. Missing only the edge cases (not-found behavior, whether all listed fields are always populated).

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 job_id parameter is already documented as 'Bilflo contract job id.' with a positive integer constraint. The description adds no format, sourcing, or lookup guidance beyond the schema, so the baseline of 3 applies.

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 the resource precisely — a single contract job, glossed as 'a contractor placed with a client' — and enumerates the fields it surfaces, plus the backing endpoint. That gloss distinguishes it from the sibling bilflo_get_contractor and bilflo_get_direct_hire, though it never names those alternatives 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?

There is no when-to-use guidance: nothing says to call this to hydrate a job record before update/terminate/reopen, and no exclusions versus list-type or adjacent getters. The only usable cue is the singular jobId in the path, which implies single-record retrieval but leaves the routing decision to the agent.

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