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

Discloses meaningful behavior beyond the annotations: the entry is unapproved, it sends no notifications ('reaches no one'), errors are recoverable via edit_time_entry, and it requires a Cotlet API key with app access. These are useful operational facts an agent needs for safe autonomous invocation.

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-loads what the tool does, then adds behavioral facts in compact sentences. Slightly dense but every sentence carries useful information with no redundancy.

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?

Covers purpose, safety profile, correction path, and auth requirement for a mutation tool with no output schema. Missing only explicit guidance on how approved status is later changed or how it relates to create_shift.

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%, so the schema already documents all six parameters. The description reinforces that start/end are ISO 8601 with time zone and that an entry is tied to one employee/job/task, but adds little beyond what the schema states.

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 (add) and resource (shift/time entry to an employee timesheet), plus scope ('the way a manager does on the web'). An agent can distinguish it from list_time_entries or approve_timesheets without opening a 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?

Gives clear context ('runs without asking', manual manager-style entry) and names the correction alternative (edit_time_entry). It stops short of explicitly contrasting with the sibling create_shift, leaving that boundary to inference.

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