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

The annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) match a tool that only returns guidance, and the description reinforces this with the key behavioral fact that it performs no action and opens nothing. It adds substantive context beyond the annotations: what the response contains and how execution must proceed.

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 actionable content is front-loaded and clear. The trailing sentence about Deputy's official REST API and lack of an MCP server is provenance trivia that doesn't help the agent decide or invoke the tool, so it dilutes an otherwise tight definition.

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 zero-parameter guidance tool with no output schema, it explains what the agent receives and the required follow-on workflow. It leaves open how shift details are supplied and what to do if the browser session is unavailable.

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?

Zero parameters, so the baseline applies; schema coverage is 100% and the description correctly avoids inventing parameter detail. It does not explain how shift specifics (employee, time, location) are conveyed to the browser tools, which is a minor gap.

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 ("Create shift in the user's own Deputy account") and immediately disambiguates that it returns step-by-step instructions rather than performing the action. It does not name a sibling alternative (e.g., deputy_list_shifts) but the instruction-vs-execution distinction is unmistakable.

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?

Explicitly prescribes the workflow: call this to get screens/buttons/fields, then execute them with the cotlet_browser_* tools in the user's Deputy Cloud Browser. It also states it "opens nothing by itself," closing off the most likely misuse.

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