delete_shared_chat_by_id_api_v1_chats

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

With no annotations, the description must fully disclose behavioral traits. It only says 'Delete' with no mention of consequences, permissions required, irreversibility, or side effects on shared state.

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 sentence that is under-specified. Conciseness should not sacrifice completeness; here it provides no useful information beyond the tool name.

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?

Despite having an output schema (unseen) and many sibling tools, the description provides no context about return values or how it differs from other delete tools. It is completely inadequate.

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%, but the description adds no value beyond the schema. The single parameter 'id' is not explained (e.g., what chat ID refers to, where to find it).

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?

Description 'Delete Shared Chat By Id' restates the tool name verbatim, offering no differentiation from siblings like 'delete_chat_by_id_api_v1_chats' or 'delete_all_user_chats'. It fails to clarify what distinguishes a shared chat from a regular chat.

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?

No guidance on when to use this tool versus alternatives. For example, it does not specify whether this deletes a shared copy or the original or when to use delete_chat_by_id instead.

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