share_rate_comment

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavior: setting liked=false removes an existing rating. It says nothing about idempotency, whether re-rating overwrites, or any auth requirements.

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?

Two short clauses, zero filler, with the core action front-loaded. It is efficient, though the extreme terseness leaves the schema to carry details that a slightly fuller sentence could have disambiguated.

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?

Output schema and annotations relieve the description of return-value and safety explanation, so the bar is lower. Still, the rating/liked interaction is left unexplained and there is no cue about what a successful rating change does or how to switch from like to hate.

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 only 33%, but the two gaps are partly self-documenting (rating is an enum like/hate; comment_id has a schema description). The description does explain the undocumented `liked` flag's cancel semantics, which is real added value. However, the interaction between `rating` and `liked` remains ambiguous — e.g. what liked=false means when rating='hate' — and is left unresolved.

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: like/dislike a comment, which distinguishes it from share_rate_material (materials) and share_report_comment (reporting). The `liked=false` undo clause is included, but the description never explicitly names its siblings or clarifies how this differs from report/delete on the same resource.

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?

There is no guidance on when to use this rather than share_rate_material, share_report_comment, or share_delete_comment. The only usage-like hint is the embedded 'liked=false cancels' note, which is really parameter behavior, not selection guidance.

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