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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the agent knows this is a safe, bounded write. The description adds the trigger context but says nothing about repeat calls (overwrite vs. append), whether the last session must exist, or what happens with a missing tap token — all of which matter for a non-read-only tool.

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?

Three short sentences, front-loaded with the trigger and followed by exclusions; no filler. The repeated 'Not for...' construction is slightly list-like but each clause carries useful routing information.

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?

For a two-optional-parameter write tool with no output schema, the description covers the trigger well but omits what the call returns and how the opaque 'tap' token should be obtained in this context. Annotations carry the safety profile, but the operational details are incomplete.

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%, so both 'tap' and 'value' are already documented in the schema, including the enum and default. The description only paraphrases the two enum values as 'liked it' / 'not for them' and adds no detail on the token's lifecycle beyond what the schema says. Baseline 3 is appropriate.

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 action — capturing whether the user liked or did not like the session they just finished — with a clear trigger tied to user speech. It does not name the closest sibling (rate_session) to distinguish itself, so it stops short of a 5.

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?

It gives an explicit when-to-use condition ('when the user says how the session they just finished was') and three explicit exclusions: medical questions, emergencies/crisis, and general chat about meditation. What it lacks is positive routing to an alternative tool for those excluded cases or a note on rate_session.

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