add_chat

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

No annotations are provided, so the description carries the full burden. It does disclose one genuinely non-obvious trait — an interactive user confirmation step — but says nothing about whether the addition is persistent, what happens if the chat_id already exists, or what permissions are needed for a mutation-style tool.

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?

Two short sentences with no waste, and the core capability is front-loaded before the confirmation note. Slightly awkward phrasing ('Allow another chat id, optionally with a name') costs it the top mark.

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?

An output schema exists, so return values need no explanation, and two parameters is low complexity. Still, for a confirmation-gated mutation the description omits duplicate handling, persistence, and the chat_id format, leaving meaningful gaps.

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. It does add real meaning for 'name' (optional, example 'ali', and crucially that it becomes alias-equivalent to chat_id), but leaves 'chat_id' completely undescribed — no format, no hint where to obtain one.

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?

It conveys the resource (a chat id) and that it becomes usable later, but the verb 'Allow' is vague — it never says this registers the chat on an allowlist, which is only inferable from siblings like list_access and remove_chat. No sibling is named, and the agent must guess whether the effect is persistent.

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?

There is no statement of when to call this versus remove_chat or add_dir, nor when to supply a name versus leaving it out. The only usage-adjacent sentence is that the user is asked to confirm, which is a behavior, not selection guidance.

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