set_my_description

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

Annotations already indicate that the tool is a write, idempotent, and non-destructive. The description adds useful behavioral context about where the description appears (empty chat). It does not contradict the annotations and is transparent about the tool's effect.

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 conveys the core purpose without any filler or redundancy. It is well-structured and front-loaded.

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 tool's simplicity (two basic string parameters, no output schema), the description provides the essential purpose but omits details about the return value and the semantics of language_code. It is adequate but not fully complete for an agent to use without prior context.

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 coverage is 0%, and the description does not mention the parameters at all. The 'description' parameter is somewhat obvious from the tool name, but 'language_code' is not explained (e.g., for localization). The description fails to add meaning beyond the schema's basic property names.

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 clearly states the action ('Set the bot's description') and provides specific context ('shown in empty chat') that distinguishes it from related tools like set_my_short_description and get_my_description. It is specific and unambiguous.

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 contextual information ('shown in empty chat') that implies when this tool is relevant, but it does not explicitly state when to use this versus alternatives such as set_my_short_description. No direct exclusions or alternative mentions are provided.

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