sigma_copy_workbook_to_member

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

Annotations already indicate a write operation (readOnly=false) and non-destructive (destructive=false). The description adds destination context but does not disclose potential side effects, permission requirements, or name conflict behavior.

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 concise sentences, front-loaded with the core action, then parameter clarification. No waste.

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?

While the core action and destination are clear, the description omits edge-case behaviors like overwriting existing files, permission requirements, or whether a folder must exist. Output schema exists but is not shown; still, a copy operation may need more context.

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 has no descriptions (0% coverage). The description explains the 'name' parameter's default behavior. It implicitly clarifies workbook_id and member_id through its phrasing, but doesn't provide explicit details.

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 explicit verb 'Copy' with specific resource 'workbook' and destination 'member's My Documents folder'. Clearly distinguishes from sibling tools like sigma_duplicate_workbook or sigma_create_workbook.

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?

No guidance on when to use this tool versus alternatives such as sigma_duplicate_workbook or sigma_deploy_template_to_folder. It does not specify prerequisites or contexts.

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