deleteChatPhoto

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

With no annotations, the description carries the behavioral burden. It discloses the required permission, a scope limitation (private chats), and the success return value (True). This covers the key behavioral aspects for a simple deletion endpoint, though it doesn't detail failure modes or edge cases like a missing photo.

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?

Three concise sentences, each carrying distinct value: the action, the limitations/prerequisite, and the return value. Front-loaded with the core purpose and no wasted words.

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 one-parameter, side-effect-focused method with no output schema and no annotations, this description covers the essential aspects: what it does, who can use it, where it doesn't work, and what it returns. Nothing critical is missing.

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 single parameter chat_id is already fully documented in the schema with 100% coverage. The description adds no further parameter-specific meaning, so the baseline of 3 applies.

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 ('Delete') with a clear resource ('chat photo'), making the operation unmistakable. It naturally contrasts with sibling setChatPhoto, so an agent can distinguish them without comparing schemas.

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?

It provides clear usage context: the bot must be an administrator with can_change_info rights, and it notes that photos can't be changed for private chats, effectively excluding private chat targets. It doesn't explicitly name alternative tools, but the prerequisite and limitation are useful guidance.

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