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

Annotations already declare readOnlyHint=true, so safety is covered. The description goes further by enumerating the returned payload (schedule, status, contact/address, totals, amount due, notes, tags, team) and citing the backing endpoint, which is real added value given there is no output schema. It omits error/not-found behavior for an invalid UUID.

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?

A single front-loaded sentence that names the lookup key first and then the payload, followed by a compact endpoint citation. No filler and nothing is buried.

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 description correctly compensates by listing the returned fields, so an agent knows what it gets back. It stops short of covering failure modes (unknown UUID, missing permissions) or any response envelope details.

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 100% and the schema already gives the UUID format with an example, so the description's 'by UUID' adds no syntax or format detail. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

States a specific verb and resource ('Fetch one job by UUID') and then enumerates what the job record contains, which cleanly separates it from workiz_list_jobs and workiz_get_lead. An agent can identify the tool without reading 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?

The phrase 'by UUID' implies the tool is used when the caller already holds an identifier, which contrasts implicitly with the list tools. However, no explicit when-to-use or when-not-to-use guidance and no sibling is named, so the routing must be inferred.

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