get_chat_gifts

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

The annotations already establish that this is a read-only, idempotent, non-destructive, open-world operation. The description adds the useful scope detail that results cover gifts both owned and hosted by the chat, but it does not explain pagination, filtering effects, or any rate/auth behavior.

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 front-loaded sentence with no unnecessary elaboration. The version tag '(v9.3)' is minor noise, and the sentence is almost too terse for the 11-parameter endpoint.

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 an 11-parameter filtered listing endpoint with no output schema and only 9% schema description coverage, the description omits pagination behavior, filter semantics, sort order, and what the result contains. Annotations cover the safety profile, but the call contract remains substantially incomplete.

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 only 9%, leaving 10 of 11 parameters undocumented, including limit, offset, sort_by_price, and the many exclude_* flags. The description adds no meaning for any of these parameters and does not compensate for the schema gap.

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 states a specific verb ('Get') and resource ('gifts') scoped to a chat, with 'owned and hosted' adding some scope detail. It does not explicitly distinguish itself from sibling tools such as get_user_gifts or get_available_gifts, and the '(v9.3)' suffix adds no selection value.

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 when-to-use, when-not-to-use, or alternative guidance despite closely related siblings like get_user_gifts, get_available_gifts, and get_business_account_gifts. An agent must infer that this tool is specifically for chat-scoped gift listings.

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