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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is structured. The description adds genuinely new operational context: authentication required and that the call is free and does not count against rate limits — information not available anywhere else. Only gap is not saying what happens when the course is already bookmarked or what the response contains.

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?

Four short sentences, each front-loading the most important fact (what it does, then auth, then cost, then idempotency). Minor waste: the idempotency sentence largely restates idempotentHint=true, though it adds the 'same course_id' clarification.

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 one-parameter, non-destructive bookmark tool with annotations covering safety and no output schema, the definition supplies the key operational facts (auth, free/rate-limit-free, idempotent). It is nearly complete; only the course_id provenance and already-bookmarked behavior are missing.

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 description coverage is 0% and the single required parameter course_id has no documented format, source, or example. The name is fairly self-explanatory, but the description does nothing to compensate — it never mentions where to obtain a valid course_id (e.g., from my_courses).

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 ('Add a course to your favorites/bookmarks') plus the resulting state ('quick access later'). The add/remove contrast with the sibling remove_liked_course is implicit in the verb but the sibling is never named, 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?

'for quick access later' implies the use case, and 'Requires authentication' is a useful precondition. However, there is no explicit when-not guidance (e.g., don't call if already bookmarked, use remove_liked_course to undo) and no alternatives are named.

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