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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by enumerating what is NOT created: no account, session, submission, diagnosis, payment or private room. That side-effect disclosure is genuinely useful beyond the annotations, and 'no private task text is accepted' warns the caller about input privacy boundaries. Return format is left to the output schema.

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?

Front-loaded with the verb and resource, then the exclusions, then the usage constraint. Three tight sentences with no filler, though the negative enumeration is long enough to slightly dilute the core purpose statement.

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 a read-only tool, one optional parameter, 100% schema coverage and an output schema describing returns, the description covers what an agent needs to decide and call correctly. Only the account_ref scoping behavior is left unexplained.

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% for the single optional account_ref, so the schema already carries the semantics. The description adds nothing about account_ref and arguably creates mild ambiguity by saying 'No account ... is opened' while an account scoping parameter exists. Baseline 3 applies.

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?

States a specific verb and resource ('Read the free Awareness Foyer') and enumerates the content returned: recognition lessons plus eight fictional practice situations with teaching feedback. It does not name a sibling alternative, but the explicit 'no account, session, quiz submission, diagnosis, pause request, payment or private room' list effectively separates it from eclypse_account, eclypse_session, eclypse_diagnostic, eclypse_pause_request, eclypse_create_invoice and eclypse_private_access.

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 exclusions act as clear when-not guidance, and 'Apply examples locally' describes the intended usage posture. What's missing is a positive routing statement (e.g. 'use eclypse_diagnostic instead if you need a personalized diagnosis'), so an agent knows where to go rather than only where not to go.

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