Get Complete Chat Information and Settings

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds an inventory of what is returned, which is useful scope context, but says nothing about rate limits, auth requirements, or per-account fan-out behavior that the annotations do not already imply.

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 tightly written sentences with no filler; the capability statement comes first, then usage scope, then the sibling routing hint in a natural priority order.

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?

With a full input schema, rich annotations, and an output schema present, the definition covers what an agent needs to select and call the tool. The only thing not addressed is any behavioral caveat for the multi-account fan-out hinted at in the schema, but nothing essential 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?

Schema description coverage is 100% for both parameters, including the accepted chat_id formats and the multi-account behavior of the optional account parameter, so the schema already carries the full burden. The description contributes no additional parameter meaning, making the baseline of 3 appropriate.

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 names a specific verb (Retrieve) and resource (complete chat information), then enumerates the concrete payload: description/about, admin rights, notification settings, and invite links. It explicitly contrasts itself with the sibling get_chat, so an agent can distinguish the two without opening either schema.

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 states the selecting condition ('Use when needing deep metadata') and names the alternative with its own condition ('For basic title and type, prefer the lighter get_chat'). This is an explicit when-to-use / when-to-use-something-else routing rule.

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