get_business_account_gifts

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing further: pagination behavior, ordering defaults, whether results are capped at limit=100, and how the many exclude_* filters interact with each other are all unstated.

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?

A single short sentence is front-loaded and free of waste, but the brevity here reflects under-specification rather than disciplined editing — nothing is said about the large filter surface.

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 11 parameters, no output schema, and no field-level documentation, this description is far too thin for the tool's complexity. An agent could call it with only business_connection_id, but could not reason about filtering or paging without reverse-engineering the schema.

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% across 11 parameters, so the description carries the full burden and does not meet it. Nine boolean-style filters (exclude_saved, exclude_unique, exclude_unsaved, exclude_unlimited, exclude_from_blockchain, exclude_limited_upgradable, exclude_limited_non_upgradable, sort_by_price) plus the offset string type are entirely undocumented, and several are wired through $ref in a way that gives no hints.

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?

States a specific verb and resource ('Get gifts owned by a business account'), and the 'business account' scope implicitly separates it from get_user_gifts and get_chat_gifts in the sibling list. No sibling is named explicitly, so the differentiation is inferred rather than asserted.

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 guidance, no prerequisites (e.g. needing an existing business connection), and no mention of the alternative gift-listing tools. An agent must guess whether to reach for this versus get_user_gifts or get_chat_gifts.

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