edit_forum_topic

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

The description adds specific behavioral detail beyond the annotations: it enumerates the mutable fields (title, closed, hidden) and clarifies that 'hidden' only affects the header for the General topic. This complements the annotations' generic mutation flags with concrete operation semantics.

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?

The description is extremely concise, with the first sentence carrying the primary purpose and the second sentence adding a critical constraint on the 'hidden' parameter. No unnecessary words 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?

The tool has 6 parameters, 2 of which are required, and an output schema. The description covers the main behaviors but omits any mention of the required parameters or the 'icon_emoji_id' field. It is minimally adequate for the core use case but not fully complete for all possible invocations.

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?

With 0% schema description coverage, the description compensates by explaining the 'title', 'closed', and 'hidden' parameters through the action verbs. However, it leaves 'chat', 'topic_id', and 'icon_emoji_id' entirely unexplained, so the compensation is only partial.

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 verb ('редактировать' = edit) and resource ('тему' = topic), and specifies the main actions: rename, close, hide. This distinguishes it from sibling tools like create_forum_topic or delete_forum_topic.

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 provides explicit context for using the hidden parameter—only valid for the General topic (id=1)—which is actionable guidance. However, it does not mention alternatives or when not to use the tool, so it stops short of a full 5.

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