edubase_post_exam_permission

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

Annotations already indicate non-readOnly and non-destructive behavior. The description adds no further behavioral details, such as whether the permission is appended or replaces existing ones, authorization requirements, or side effects (e.g., affecting user access immediately).

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, straightforward sentence that conveys the essential purpose without unnecessary words or structure. It is appropriately front-loaded.

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 description covers the basic action and parameters are well-documented in the schema, it omits important context such as idempotency (annotations show false), the fact that the tool likely requires existing exam and user, and any potential behavior when permission already exists. An output schema exists but is not provided; still, the description is minimally sufficient for a simple creation tool.

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 schema provides detailed descriptions for all three parameters, including an enum for 'permission'. With 100% schema coverage, the description adds no significant new semantic information beyond stating the action. 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 clearly states the action ('Create'), the resource ('permission'), and the target ('exam' and 'user'). It effectively distinguishes this tool from sibling tools like edubase_delete_exam_permission (deletion) and edubase_get_exam_permission (reading permissions).

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 provides no guidance on when to use this tool versus alternatives, such as edubase_post_exam_permission compared to edubase_post_exam_users or permission updates. It also lacks prerequisites (e.g., existence of exam and user) or scenarios where this tool is appropriate.

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