provider_query_certificate_library

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 fully covered. The description adds only the raw endpoint path, which merely restates the annotation title, and says nothing about pagination behavior, default page size, or whether the list is complete or truncated.

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?

Two of the three lines are near-verbatim repetitions of each other and of the tool name, and the third is a bare URL. Nothing is front-loaded beyond the name restatement, and no sentence earns its place by adding 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?

This is a paginated list operation with two required pagination parameters and no output schema, yet the description says nothing about what a certificate library item contains or how paging/result totals behave. The only real context comes from the annotations and schema, leaving the description inadequate for a tool whose return shape is undocumented.

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% with all five parameters (page, pageSize, filter, sortAsc, sortDesc) documented in the schema itself. The description adds no meaning beyond that, so the baseline of 3 applies for schema-carried semantics.

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 does name a verb and resource ('Get a list of the certificate library items'), but it says the same thing twice and adds a raw HTTP path rather than clarifying scope. It never distinguishes itself from close siblings such as provider_get_certificate_library_item (singular), provider_query_cert_library_item_consumer_refs, or provider_add/delete_certificate_library_item.

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 when-to-use guidance, no exclusion, and no named alternative. An agent cannot tell from the text whether this should be preferred over provider_get_certificate_library_item or when to reach for the consumer-refs query instead.

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