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

Annotations already flag destructive, non-idempotent, open-world behavior; the description adds real context beyond that — the confirmed=true / impactConfirmed=true double gate, internal header resolution, automatic stripping of internal-only fields, and that UserDevice must be omitted rather than invented. It doesn't explain job lifecycle or failure semantics for the queued migration.

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?

Front-loads purpose and usage well, but includes boilerplate that earns little ('This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller', 'Search terms: listing migratebulk') and repeats the required-flag rule already encoded in the schema.

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 a destructive bulk mutation, the description covers the confirmation gates, auth/channel resolution, body composition, and output effect, with an output schema covering return values. Missing only escalation/failure context (e.g., what happens if some listing ids are invalid).

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 coverage is 100%, but the description adds substantive meaning: it enumerates the MigrateBulkRequest body fields (ListingIds, TargetId, listFrequencyMinutes, dontListUntil, reviewBeforePublishing, createdBy, and the ignore/optimize flags) and warns against inventing the UserDevice telemetry value. That goes meaningfully beyond the terse schema descriptions.

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: 'Queues selected listings for migration to a target channel in bulk,' and disambiguates from a generic endpoint caller. It does not explicitly contrast with the closest sibling (hgr_post_listing_relistedbulk2), so it stops short of 5.

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?

'Use when: concrete listing ids and a target channel are already selected and the user wants to migrate/copy them in bulk' gives a clear trigger, and it names the prerequisite that channelOAuthId must come from hgr_list_channels. No explicit 'when not to use' or named alternative, so not 5.

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