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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description's only added claim is auth context ("Requires HGRApi Header channel / ChannelOAuthId resolved internally"), but that misleads: the channelOAuthId is a required caller-supplied parameter, not resolved internally. Nothing about scope, volume of DIDs returned, or pagination is disclosed.

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?

Heavy boilerplate: a disclaimer that it is "not a generic endpoint caller," a duplicated Purpose/Use-when/Input/Output block, and a trailing "Search terms" line. The one useful signal (channelOAuthId) is drowned out and is contradicted by the Input line.

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?

An output schema exists so return values need no prose, and annotations cover safety. But for a single-parameter tool the description should at minimum explain what the DID list is and confirm the required auth parameter; instead it asserts no input is needed, leaving the agent with less accurate information than the schema alone.

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% and the channelOAuthId description already explains it comes from hgr_list_channels, so the schema does the work. The description actively contradicts it by claiming "No explicit input parameters required," which could cause an agent to omit a required argument.

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 restates the tool name ("Provides the GET did list operation") without ever explaining what a "did list" is or what data the caller receives, so the core resource is opaque jargon. It does name the underlying endpoint GET api/Listing/DidList, but that adds no meaning an agent could not infer from the tool name itself.

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 it when a client needs to run the did list operation for bulk publication and publication tracking" is circular — it tells the agent to use the tool when it needs to use the tool. No sibling is named (e.g. hgr_get_listings, hgr_get_active_listings, hgr_post_listing_getbulkhistory), and no when-not or prerequisite conditions are given.

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