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

The key behavioral fact an agent cannot infer from annotations — that existing bookings are NOT carried over — is disclosed explicitly, preventing a wrong assumption about data loss. Remaining gaps (permissions required, what is returned, whether the original is untouched) are minor since annotations already declare it non-read-only, non-destructive, non-idempotent.

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?

Two short sentences with zero filler; the what-it-copies fact leads and the use case follows. Nothing could be cut without losing 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?

For a two-parameter duplication tool with annotations and no output schema, the description covers enough to call it correctly. It would be stronger if it noted that the new schedule's identifier is what you get back, since follow-up work depends on it.

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%, and the schema even points to where each ID comes from (get_schedulers, workspace://list). The description adds no parameter detail beyond that, so the 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 ("Copies a booking schedule") and immediately scopes what is and isn't duplicated, which separates it from save_scheduler/create semantics. It never names a sibling tool explicitly, so the differentiation is implied rather than stated.

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 a concrete context for use ("handy for a similar schedule with another length or other hours"), which tells the agent when this is the right call. It stops short of exclusions or naming an alternative (e.g., save_scheduler for building one from scratch).

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