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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: an auth requirement ('Needs the user's Cotlet API key with access to this app') and a clarification that financial totals are the as-shown figures. It omits return format/pagination detail, but the added auth note is real value.

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 list of returned fields is effectively stated twice ('Full job: contacts, address, trade and work type, milestone history, sales owner and financial totals' then 'Returns one job with its contacts, job site address, trade and work type, sales owner and the milestone history in order'). The redundant second sentence wastes space, though the conclusion (use job_id, auth requirement) is useful.

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 carries the return-value burden and largely does so by enumerating the returned fields and noting the ordering of milestone history. The auth requirement and ID source are covered; only minor gaps like response shape details remain.

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 single job_id parameter is already documented in the schema. The description only restates 'use the job_id from list_jobs,' adding no syntax beyond the structured field, so the baseline of 3 is correct.

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 a specific verb (get) and resource (job), then enumerates the exact payload: contacts, job site address, trade/work type, milestone history, sales owner and financial totals. An agent can distinguish it from acculynx_list_jobs (which returns many) and acculynx_update_job_milestone (a mutation) without opening either 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?

It gives the prerequisite chain explicitly: 'Use the job_id from list_jobs,' which tells the agent how to obtain the required input. It does not name explicit when-not or alternative tools, so it falls short of the 5 tier, but the context is clear.

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