update_assignment

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

With no annotations, the description carries the burden and does disclose one behavioral trait: publish state is untouched. However, it does not mention partial update semantics, null handling, permissions, or return values, leaving significant gaps.

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, no filler. The first sentence establishes the operation, and the second adds a valuable caveat. Concise and front-loaded, though arguably too brief for the tool's complexity.

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?

Given 6 parameters, no annotations, no output schema, and many sibling tools, the description is incomplete. It does not explain which fields are updatable, whether nulls clear fields, or what happens to unspecified fields, so the agent is left with insufficient 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?

The description does not mention any parameters. With schema description coverage at 0% and 6 parameters, the description fails to add meaning beyond the raw schema field names.

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 'Update an assignment' which is a clear verb+resource combination, and adds a scope clarification ('Publish state is left alone'). It distinguishes from create_assignment but not from set_due_dates or other update-like tools.

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 implies the tool is for modifying assignment fields, but provides no explicit when-to-use guidance, exclusions, or alternatives. The context is clear but the guidance is minimal.

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