set_chat_description

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It conveys that the operation is a mutation ('Change'), but it does not mention side effects, permission requirements, idempotency, or what happens to the previous description. This is minimal context.

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, direct sentence with no filler words, front-loading the core action. It is efficient, though additional sentences could have enriched it without significant verbosity.

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 two required parameters, no annotations, no output schema, and zero schema description coverage, the description is far too sparse. It lacks usage context, parameter semantics, behavioral impacts, and any mention of permissions or related alternatives. An agent would need substantial external inference to invoke this confidently.

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 for parameter meaning. The phrase 'a chat's description' loosely implies the 'description' parameter holds the new text, but 'chat_id' is not explicitly linked to the target chat, and no formats, constraints, or error conditions are given.

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 uses a specific verb ('Change') and a clear resource ('a chat's description'), making the tool's primary function immediately obvious. It also differentiates from sibling tools like set_chat_title and set_chat_photo, which target different chat attributes.

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?

No guidance is provided about when to use this tool instead of other chat-related siblings, nor any prerequisites such as required permissions. The description simply states the action without contextual cues about appropriate situations.

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