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 genuine behavioral context by noting the Cotlet API key must have access to this app, but says nothing about return format, pagination, or missing-record behavior beyond annotations.

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?

Front-loaded with the resource and its field list, which is good, but the field enumeration is essentially repeated twice ('Full job: description, scope of work, charges...' then 'Returns one job or opportunity with its internal description, the customer-facing scope of work, charges with the running total...'). The redundancy wastes space without adding new information.

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 burden of describing return contents and does so thoroughly for a read tool. Auth requirements are stated and the single input is well covered by the schema; only minor gaps like error/missing-job handling 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?

Only one parameter and schema coverage is 100%, so the schema already documents job_number and its source (list_jobs, list_opportunities, get_job). The description adds no syntax or format detail beyond what the schema provides; baseline 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?

States a specific verb and resource ('Get job') and enumerates exactly what the tool returns (description, scope of work, charges, schedule events, time entries, notes, invoice status). It clarifies it returns 'one job or opportunity', distinguishing it from the list tools, but never names kickserv_list_jobs or kickserv_list_opportunities as the alternatives.

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 only implied: fetch a single job/opportunity. There is no explicit 'when to use this vs list_jobs/get_customer' guidance and no stated prerequisites for choosing this lookup tool, though the single-record nature makes the intent inferable.

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