set_topic

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

No annotations are provided, so the description carries the full transparency burden. It reveals the empty-string deletion behavior, which is helpful, but omits mutation implications such as permissions, overwriting of existing topics, side effects, or response behavior. For a write operation, this is a significant gap.

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?

Exactly two sentences, no filler, and the most important behavioral note (empty string deletes) is included. Every word earns its place; the description is ideally concise.

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?

The tool is conceptually simple and the description covers its core purpose plus a key edge case. However, it lacks usage context, parameter elaboration, and mutation details, making it only minimally complete for an agent that must invoke it correctly in varied situations.

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%, so the description must compensate. It implicitly references the topic and change_id meanings but does not explicitly explain any of the three parameters, including the optional gerrit_base_url. The context clues are thin and do not fully disambiguate parameter roles.

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 clear action verb ('Sets') and specific resource ('topic of a change'), and distinguishes the behavior with the notable edge case of an empty string deleting the topic. This unambiguously differentiates it from sibling tools like set_ready_for_review or set_work_in_progress.

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?

The description gives no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It merely states what it does, leaving the agent to infer usage from the tool's name and sibling context.

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