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

Adds context beyond annotations: requires confirmed=true before execution, channel resolved internally, internal-only fields stripped, and AI/MCP must omit UserDevice rather than invent one. Annotations already cover destructive/openWorld/non-idempotent, so these operational preconditions are the genuinely additive part.

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 ('Dedicated HGRApi tool for POST...', 'Search terms: listing saveautolist', 'Send the exact request payload in body') and restates an output shape that an output schema already documents.

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?

Covers payload semantics, confirmation requirement, channel resolution and telemetry omission, which is enough to invoke correctly for a destructive bulk-write tool with rich schema and output schema. Minor gaps: no quota/rate-limit detail despite mentioning quota-related counts, and no explicit distinction from the nearest bulk-publish siblings.

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% (baseline 3), but the description goes well beyond it by enumerating the SaveAutolistRequest fields and, crucially, explaining that each listings row is [sourceUrl] or [sourceUrl, optionalTitle], that sourceUrl is required, and that an omitted/null/empty title means no custom title while a supplied title is preserved.

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: 'Saves a bulk/autolist publication batch' via POST api/Listing/SaveAutolist, and clarifies it is an explicit fixed-endpoint tool rather than a generic caller. It does not, however, explicitly distinguish itself from close siblings such as hgr_post_listing_autolist or hgr_post_listing_savebulkpublish.

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: Use when the user wants to queue multiple source URLs for publication or review through the autolist/bulk listing flow' gives a clear triggering condition. It lacks explicit when-not or named-alternative routing against the other bulk/autolist siblings.

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