edubase_get_class_permission

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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds value by clarifying the exact operation is checking a specific permission for a specific user on a class. It does not contradict annotations and aligns well with the safe, read-only behavior implied.

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, clear sentence that efficiently conveys the tool's purpose. Every word is necessary, and it is front-loaded with the key action and resource. No unnecessary fluff.

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 the presence of an output schema (which presumably describes the boolean result), the simple description is sufficient. The tool's purpose is straightforward: checking a permission. The context signals (100% schema coverage, annotations) support completeness.

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% with all three parameters (user, class, permission) described. The description adds no additional parameter detail beyond what the schema provides. The enum for permission (view/report/control/modify/grant/admin) is well-defined in the schema.

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 'Check if a user has permission on a class' uses a specific verb ('Check') and clearly identifies the resource ('user') and target ('class'). It directly mirrors the tool name and is distinct from siblings like edubase_post_class_permission (which sets permissions) and edubase_delete_class_permission (which removes them).

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 implies this tool is for checking existing permissions, not setting or deleting them. It differentiates clearly from sibling tools like edubase_post_class_permission and edubase_delete_class_permission by being a 'check' rather than a mutation. However, it does not explicitly state when NOT to use it or provide alternatives.

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