verify_chat

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

Annotations already declare idempotentHint=true, destructiveHint=false, openWorldHint=true, and readOnlyHint=false, which cover the safety profile. The description adds the organizational context but no further behavioral traits like effects, reversibility, or permissions. It does not contradict annotations.

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 immediately states the action and scope. There is no redundant wording or unnecessary detail, making it efficient and easy to parse.

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 two-parameter mutation with no output schema, the description is minimally adequate but leaves clear gaps. The semantics of custom_description are unexplained, and there is no mention of response behavior or when to use this over related tools. Annotations mitigate some concerns but not all.

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 describes chat_id ('Chat ID or @username') but custom_description only has a maxLength constraint without meaning. The tool description adds no explanation of parameters, so the agent is left without context for custom_description. Schema coverage is only 50%, and the description fails to compensate.

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 ('Verify'), the resource ('a chat'), and the scope ('on behalf of the bot's organization'). It distinguishes from sibling tools like verify_user by specifying the resource type, making the purpose 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 provides no guidance on when to use this tool versus alternatives such as verify_user or remove_chat_verification. It lacks any prerequisites, exclusions, or contextual cues beyond the basic action, so the agent cannot infer appropriate usage situations.

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