edubase_post_user_login

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

The description explains that existing valid links are reused, indicating idempotency-like behavior. However, annotations set idempotentHint=false, creating a contradiction. No details on authorization, rate limits, or side effects beyond the annotations.

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?

Two sentences with no redundancy. First sentence states the purpose directly; second sentence clarifies a key behavioral trait. Maximally efficient.

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 output schema exists, the description does not need to detail return values. It adequately covers the core behavior and references the link reuse behavior. However, it could briefly mention that this is for authentication or that it's a POST operation.

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 all seven parameters described in the schema. The description adds no extra parameter-level meaning or interaction details.

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 'Generate login link', specifying the verb and resource. Among siblings, this tool is distinct as the only one for creating/retrieving login links, with edubase_get_user_login and edubase_delete_user_login covering retrieval and deletion.

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 on when to use this tool versus alternatives like get_user_login or other authentication methods. No mention of prerequisites or context.

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