create_assignment

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

With no annotations provided, the description carries the burden of behavioral disclosure. It usefully discloses the permission requirement and the special web_mode/quantity -1 behavior. However, it does not describe output behavior, side effects, or consequences of unspecified parameters, which matters for a creation operation.

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 description is two tight sentences with no filler. The primary action comes first, followed by the special capability and permission requirement, making it easy to scan.

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?

This is a complex 12-parameter tool with no annotations and no output schema, yet the description provides only minimal context. It leaves many optional parameters, expected behavior, and alternatives unexplained, so an agent cannot safely infer full usage.

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 only 25%, so the description must compensate. It adds meaning for web_mode and quantity by explaining the open-web-link use case, but 12 parameters exist and most remain unexplained in both schema and description. This is partial compensation at best.

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 clearly states the tool creates a Survey Solutions assignment, naming a specific verb and resource. It also highlights the special open-web-link capability, which helps define the tool's scope. However, it does not explicitly distinguish this tool from the sibling create_external_test_link.

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?

The description gives no guidance on when to use this tool versus alternatives such as create_external_test_link or other assignment-related tools. It mentions required permissions, which is contextual, but not when to choose or avoid this tool.

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