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

Beyond the annotations (which only signal a non-destructive write in an open world), the description discloses that the copy is invisible and silent ('Nobody sees it and no one is told, so it runs without asking first'), plus the API-key requirement. That is meaningful side-effect and auth context. It does not describe what the call returns or the new ID, which is the remaining gap.

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 and readable, but wasteful: 'Copy a sign-up with a new title. The copy is an unpublished draft.' is restated almost verbatim in the next sentence ('saves the copy as an unpublished draft under the new title'). Roughly a third of the text is repetition.

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 write tool with no output schema, the description covers the important facets: resulting state, visibility/notification behavior, missing confirmation prompt, auth prerequisite, and the follow-up publish caution. Only the return payload is unaddressed, which is acceptable given there is no output schema.

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 all three parameters are already documented in the schema. The description only echoes 'under the new title' for the title param and adds nothing about group_id or the signup_id source, so 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?

The description states a specific verb and resource — 'Copies a sign-up, past or active, with its slots' — and disambiguates the result state ('unpublished draft'). An agent can distinguish it from signupgenius_create_signup and signupgenius_publish_signup without opening schemas.

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?

It gives clear operational context: the copy is a draft, and the agent should 'Check the dates on the copy before you publish it,' implying a publish step follows. It does not explicitly name alternatives (e.g., create_signup) or state when not to duplicate, so it stops short of full when/when-not coverage.

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