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

Annotations declare destructiveHint=false but leave readOnlyHint=false; the description's 'Changes nothing' supplies the crucial safety fact the agent needs (this lookup is side-effect free) despite the default read-only flag. It does not say what the tool returns or how a 'no account' case is expressed, which the agent must know to act on the result.

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?

Very short and front-loaded: the check is stated first, the timing guidance second, the no-side-effects guarantee last. The fragmentary opening sentence is slightly awkward but wastes no 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?

With no output schema, the description should indicate whether the answer comes back as a boolean, found/not-found status, or a student record. As written, the agent knows what to ask but not how to interpret the response, which is a meaningful gap for a lookup tool.

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?

One required parameter with 0% schema description coverage, so the description carries the burden: it makes clear the input is an e-mail address of a prospective student. Nothing is said about format or validation, but the semantics are fully inferable.

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 states a specific behavior: testing whether an e-mail already has an account in Trainer Connect. It distinguishes itself from the invite flow by framing itself as a pre-check. It is slightly indirect (a 'Whether...' fragment rather than a verb like 'Check'), but the intent is unambiguous.

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?

'before inviting the student' gives a concrete trigger point and implicitly points at invite_student/create_student as the follow-up action. No explicit when-not or edge-case handling is given, but the calling context is clear.

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