edit_general_forum_topic

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

The description states that only the name is edited, which is consistent with annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false). It adds no additional behavioral context beyond the annotation-provided safety profile.

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, front-loaded sentence with no unnecessary information. It is instantly understandable and well-scoped.

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 2-parameter mutation with no output schema, the description adequately covers the essential scope and purpose. It does not need to explain return values or complex behaviors, though it could mention prerequisites like admin rights.

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 50%: chat_id has a description but name does not. The description partially compensates by indicating 'name' is the new name of the General topic, but does not elaborate on format or constraints beyond schema min/max length.

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 uses specific verb 'Edit' and clearly identifies the resource: 'name of the ''General'' forum topic'. This distinguishes it from sibling tools like close_general_forum_topic or edit_forum_topic, which serve different purposes.

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 implies usage for renaming the General forum topic, but does not explicitly mention alternatives or when not to use it. It lacks direct comparison with edit_forum_topic or other topic-related tools.

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