edubase_post_user_assume

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

Annotations are all false, providing no hints. The description implies a state change (affects subsequent requests) but does not elaborate on side effects, idempotency, or error scenarios. Some behavioral context is added but remains vague.

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?

A single sentence that efficiently conveys the core function. It is front-loaded with the purpose. Could benefit from slightly more detail without being verbose.

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 that there are only two parameters and an output schema exists, the description is incomplete. It does not explain the assume token concept, the output format, or how the state change affects subsequent requests. An agent would lack key context.

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 coverage is 100%, with descriptions for both parameters in the schema. The description adds no extra meaning beyond the schema, so it meets the baseline but does not enhance understanding.

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 what the tool does: 'Assume user for next requests with assume token.' It identifies the action (assume user) and the resource (next requests). The name also reinforces the purpose. However, it could be more precise about what 'assume token' means.

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_post_user_login or edubase_delete_user_assume. The description does not mention prerequisites, context, 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.