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

The readOnlyHint annotation already establishes the safe-read profile, and the description adds useful context beyond it by enumerating what comes back (schedule, status, client contact/address, source, notes, assigned team) and citing the underlying endpoint GET /lead/get/{UUID}/. It omits auth requirements, error behavior for an unknown UUID, and pagination/formatting details.

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 sentences with the identifier and return payload front-loaded; no filler or restated boilerplate.

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, and the required UUID input is unambiguous. Slightly short of complete because it says nothing about failure cases or the shape/format of the returned data.

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 uuid parameter is already documented with an example, so the description's 'by UUID' adds nothing beyond the schema. Baseline 3 is appropriate.

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 (Fetch) and resource (one lead) scoped by UUID, which implicitly distinguishes it from workiz_list_leads. It does not explicitly name a sibling or contrast against the other lead tools, so it stops short of a 5.

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?

Usage is implied: call this when you have a lead UUID and need a single lead. There is no explicit when-to-use/when-not guidance and no mention of the alternative (workiz_list_leads) for retrieving multiple leads.

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