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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds real value beyond them: it discloses that the entry reaches no one, that an admin can delete it (reversibility), the confirmation policy, and the auth requirement ('Cotlet API key with access to this app'). It does not describe return structure beyond 'returns it', but the side-effect and auth disclosure is substantive.

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?

Four sentences, purpose front-loaded, with no filler. The auth/permission sentence is useful, though 'It reaches no one' is slightly awkward phrasing that could be tighter.

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?

For a 6-param mutation tool with no output schema, the description covers purpose, side effects, reversibility, confirmation policy, and auth needs. It is close to complete; only richer return/pagination context is absent, which is minor.

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%, so the schema already documents all six parameters including the decimal format and job_number sourcing. The description's only added detail, 'Hours are a decimal,' duplicates the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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: 'Record hours worked on a job by an employee' and 'Adds a time entry to the job.' This clearly distinguishes it from siblings like kickserv_add_charge or kickserv_create_job without needing to open any 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 description implies usage context ('it runs without asking first') but never names an alternative or a when-to-use versus when-not condition relative to sibling tools such as kickserv_add_charge or houzz-pro_log_time. Usage is implied rather than explicit.

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