comment_toggle_spam

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

Annotations already provide readOnlyHint=false (mutation), destructiveHint=false, idempotentHint=true. The description adds context about the endpoint structure and body format, but does not contradict annotations. It provides moderate additional behavioral context beyond annotations.

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 sentences, front-loaded with the core action. No extraneous text. Every sentence adds value.

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 simple toggle tool with four parameters, good annotations, and no output schema, the description is fully sufficient. It covers purpose, usage distinction, and provides endpoint context.

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 75%, with three parameters having descriptions. The description mentions the is_spam parameter and flat body, but adds little extra meaning beyond the schema. Baseline of 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?

Description clearly states the action: 'Flip a comment's spam flag'. It specifies the HTTP method and endpoint, and distinguishes from sibling tools by noting 'For other field edits use voog_admin_api_call (rare)'. The verb 'Flip' is specific and the resource 'comment's spam flag' is unambiguous.

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?

Explicitly tells when to use this tool ('Flip a comment's spam flag') and when not to ('For other field edits use voog_admin_api_call (rare)'). Also mentions that Voog's moderation UI uses this endpoint, reinforcing its intended use case.

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