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

Goes well beyond the idempotentHint/destructiveHint annotations by disclosing that retrying the same state creates no duplicate reaction or notification, that a new like notifies the original author (conditionally on membership), and by listing the returned fields. This is rich, non-obvious behavioral context.

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 front-loaded sentences, each carrying distinct information (purpose, precondition, idempotency/notification behavior, return payload) with no filler or repetition.

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 present, the description usefully enumerates return fields (item_id, liked, like_count, changed) and covers preconditions, idempotency, and side-effect notifications. Nothing material for correct invocation is 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 100% and the schema already explains both parameters (liked semantics, item_id formatting/uuid). The description's 'set the desired liked state' mirrors the schema rather than adding new syntax or format detail. 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?

States a specific verb (like/unlike) and a precise resource (another member's visible AccountHub shared project item), which separates it from sibling reaction tools like add_reaction/remove_reaction that operate on messages. An agent can identify the target scope without opening the schema.

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?

Gives a clear precondition (requires active membership) and scopes the target to another member's visible item, which implies when this applies. It does not, however, name the alternative tools (add_reaction/remove_reaction) or state when NOT to use it, so the routing guidance is contextual rather than explicit.

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