edubase_patch_exam

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

Annotations already cover the safety profile (non-readonly, non-destructive, idempotent), so the bar is lower. The description adds meaningful behavior beyond annotations, notably the start-time mutation limit and the boundary that settings updates belong to a different endpoint.

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 compact: two sentences, no filler, and the most important scoping information is front-loaded in the first sentence. Every clause contributes either resource identification, a usage boundary, or a temporal constraint.

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?

Rich parameter descriptions in the schema plus the description's scope and constraint are enough for an agent to invoke this tool correctly. No output schema exists, but the return value is not necessary to decide whether or how to call this endpoint.

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 the input schema already documents each parameter, including formats, removal semantics, and constraints. The description restates the parameter list but adds no meaning beyond what the schema provides, so baseline 3 is appropriate.

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 uses a specific verb ('Update') and clearly identifies the resource: an existing exam. It enumerates the exact editable fields (title, external identifier, language, description, organization, start/end times, deadline), and its closing note distinguishes this tool from the settings endpoint.

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 explicitly tells the agent when to use this tool (to update exam details) and when not to (to change settings, use edubase_post_exam_settings). It also includes a clear temporal exclusion: the start time can only be changed until the first result arrives.

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