exams_update

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

With no annotations provided, the description must fully disclose behavioral traits. It only states 'Update an existing exam,' implying a mutation, but fails to indicate if the update is partial or full, what happens on error, or whether it requires specific permissions. This is insufficient for safe invocation.

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 a single short sentence, which is concise but lacks substance. While it avoids verbosity, it does not add value beyond the tool's name. It is minimal but not tautological, earning a mid-range score.

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 no output schema, no annotations, and minimal input description, the description fails to provide complete context for a mutation tool. It does not address return values, error scenarios, or the scope of updates, making it inadequate for correct 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?

The input schema has 0% description coverage for its single parameter 'id', and the description does not mention or explain this parameter. The description 'Update an existing exam' does not clarify that the exam ID is required or how to supply updated fields, leaving the agent without essential usage 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?

The description clearly states the verb 'Update' and the resource 'exam', making the tool's purpose unambiguous. However, it does not differentiate from sibling tools beyond the name, which is acceptable since 'exams_update' is the only update tool for exams. The lack of detail on what fields can be updated slightly reduces clarity.

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 is provided on when to use this tool versus alternatives like exams_create or exams_delete. There is no mention of prerequisites (e.g., exam must exist) or context such as typical workflows, leaving the agent without sufficient decision-making information.

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