edubase_post_course_permission

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

Annotations already provide key behavioral hints (readOnlyHint=false, destructiveHint=false). The description adds only 'Create new permission', which is already obvious from the name. It does not disclose whether existing permissions are replaced, whether authorization is needed, or any side effects beyond the basic mutation.

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 with no filler. It is appropriately concise but does not attempt to provide richer context. For a minimal viable description, it earns a 4 for efficiency.

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?

Despite having an output schema and full parameter descriptions, the description lacks critical context for a permission creation operation. It should clarify whether the tool is additive or replaces existing permissions, and mention that user and course must be valid identifiers. The openWorldHint=true suggests creation without strict preconditions, but the brevity leaves 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?

Schema description coverage is 100%—all three parameters have descriptions in the input schema. The description does not add any new parameter-level information, so the 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 'Create new permission for a user on a course' clearly states the action (create), the object (permission), and the context (for a user on a course). It distinguishes this tool from sibling permission tools like edubase_post_class_permission or edubase_post_exam_permission by explicitly naming the resource type 'course' and the user target.

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 given on when to use this tool versus alternatives. There are many sibling permission creation tools (for class, exam, quiz, etc.), but the description does not help an agent decide between them. It also omits prerequisites (e.g., user and course must exist) or when not to use it.

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