edubase_post_course_permission

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

The description only says 'Create new permission', which implies a non-read-only operation (consistent with readOnlyHint=false). However, it does not disclose what happens if the permission already exists (e.g., error, update), side effects, or authorization requirements. Annotations do not contradict, but the description adds minimal behavioral context beyond the word 'Create'.

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, front-loaded sentence that efficiently conveys the tool's purpose. While very brief, it contains no wasted words.

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?

For a simple create tool, the description is minimally adequate. An output schema exists (not shown) so return values are covered. However, it lacks prerequisites (e.g., course and user must exist) and fails to differentiate from sibling permission tools, leaving the agent underinformed.

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 fully describes all 3 parameters with clear descriptions and an enum for permission. The description does not add any additional meaning beyond the schema, meeting the baseline for high schema coverage.

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') and the resource ('new permission for a user on a course'). It directly matches the tool name and distinguishes this from other post_permission tools (e.g., for classes, exams) by specifying 'course'.

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 edubase_delete_course_permission or other post_permission tools. The agent must infer usage from context.

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