provider_query_cert_library_item_consumer_refs

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only that results are paged and returned as references; it says nothing about pagination limits, sort/filter behavior, or what happens for an invalid item id.

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?

The core purpose is front-loaded, but the first two sentences are near-verbatim duplicates and the third line is a raw endpoint path that adds little for an agent. Short overall, but a third of the text is redundant.

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 no output schema, the description should carry more of the return-value burden; it does indicate a paged list of consumer references, which is the essential shape. It omits what a consumer reference contains and whether results can be empty, leaving a moderate gap for a read tool with six parameters.

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 100%, so the schema already documents page, pageSize, filter (FIQL), sortAsc, and sortDesc. The description contributes no additional meaning about pagination defaults or filter syntax, so the baseline 3 applies.

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 states a specific verb and resource: a paged list of consumers (as references) of a particular certificate library item. It is unambiguous about what is returned, though it never distinguishes itself from siblings like provider_get_certificate_library_item or provider_replace_cert_library_item_consumer_refs.

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 guidance on when to use this versus the closely related sibling provider_replace_cert_library_item_consumer_refs or provider_add_consumer_ref_to_cert_library_item, nor any statement of prerequisites (e.g. that the certLibraryItemId must exist). The agent must infer usage entirely from the name.

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