close_general_forum_topic

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

The description adds no behavioral context beyond what the annotations already imply. While annotations indicate it's a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false), the description does not mention side effects like the topic being hidden or the need for admin permissions, nor whether it can be undone by reopening.

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 a single, concise sentence that is immediately front-loaded. It avoids unnecessary words, but it is so brief that it nearly restates the tool name. Still, it's appropriately sized for a simple action, though it sacrifices completeness for brevity.

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?

Given the simple schema (one parameter) and annotations, the description is not complete enough. It lacks context about when to use this tool (e.g., in a supergroup with the General topic), what closing entails (e.g., it hides the topic for users), and how it relates to sibling tools like reopen_general_forum_topic. This is a minimal description that leaves an agent guessing.

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?

The schema covers the one parameter (chat_id) with a description 'Chat ID or @username', so schema coverage is 100%. The tool description adds no additional meaning about the parameter, but the baseline of 3 is appropriate because the schema is self-sufficient.

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 'Close the 'General' topic.' clearly identifies the action (close) and the resource (the General topic). It distinguishes from siblings like close_forum_topic by specifying 'General'. However, it's terse and doesn't mention that this applies to a specific chat, relying on the parameter for that context.

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 tool versus alternatives such as close_forum_topic or reopen_general_forum_topic. The description doesn't mention prerequisites, such as the chat being a supergroup or needing admin rights, nor does it say it's for closing the default topic only.

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