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

Annotations already flag this as a non-read-only, open-world mutation; the description adds genuinely useful context: it returns a count of shifts published, it reaches other people, confirmation is on by default, and it requires the user's Cotlet API key. It doesn't state reversibility or failure behavior, so not a 5.

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 core action, but sentence two and three are redundant: 'so they appear in employees' mobile app' then 'Employees see published shifts in their mobile app.' That repetition costs structure without adding meaning.

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 mutation tool with no output schema, the description covers effect, return value (count), confirmation behavior, and auth requirements. It is complete enough to call correctly, missing only edge cases like what happens to already-published shifts or partial failures.

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 from/to and shift_ids are already documented. The description reinforces the range-vs-named-shifts semantics but adds no format or default detail beyond the schema, matching the baseline 3 when 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 (publish) and resource (draft shifts) plus the concrete outcome (shifts appear in employees' mobile app). An agent can distinguish this from clockshark_create_shift and clockshark_list_shifts without opening 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?

Explains when to use it: to publish named shifts or all drafts in a date range. It implies the draft-shift condition that makes this the right tool but never names an explicit alternative or a when-not-to-use case, so it falls short of a 5.

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