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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the returned payload scope (status plus result) and the endpoint path, but says nothing about whether polling is expected, how long batches take, or what the result looks like structurally.

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?

Three short sentences, front-loaded with purpose, followed by the actionable parameter hint and the endpoint for traceability. Nothing is redundant and nothing could be cut without losing information.

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 two-parameter read-only lookup with full schema coverage and no output schema, the description covers purpose, states, and the optional error-expansion flag. The only gap is that no output schema exists and the description does not sketch the shape of the returned result, leaving the agent to discover it at call time.

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%, so the baseline is 3, but the description adds real meaning: the schema says only 'Include the details of each error', while the description clarifies these are per-member errors for a bulk member operation. That extra specificity helps the agent decide when to enable the flag.

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+resource: fetches the status of a bulk batch job, and enumerates the possible states (NEW, PROCESSING, COMPLETED) plus the result payload. It does not need to differentiate from named siblings because no other batch-related tool exists in the sibling list, so it is clear without being maximally explicit.

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?

Usage is only implied – an agent infers this is the tool to poll when tracking a bulk job, but there is no statement of when to call it versus other tools or of prerequisites (e.g. where the batch_id comes from). The one conditional hint, setting show_error_details, is genuinely useful guidance for a specific scenario.

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