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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that with the advisory clause ('it never changes how a request is decided'), clarifying that the catalogue is informational and has no effect on request routing. It does not describe pagination defaults or return size beyond what the schema implies.

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 sentences that are front-loaded with the listing behavior, followed by the use case and the advisory caveat. Each sentence carries weight and there is no padding, though the middle use-case sentence slightly interrupts the flow of the two behavioral statements.

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 read-only catalogue tool with no output schema, the description explains entry granularity (one per tool and source) and entry contents well enough for an agent to interpret results. The absence of output schema is largely compensated, though pagination and total-count behavior are left to the schema.

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 every one of the six parameters is already documented in the schema. The description adds no filtering syntax, default values, or interaction between parameters, so the baseline 3 is appropriate.

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 ('List the tools agents have reported or can reach') and details the shape of each entry (schema, offering instances, source availability). It is clear what the tool returns, but it never distinguishes itself from close siblings like get_tool_catalog_entry or list_tool_definitions, so an agent still has to infer which is the right one.

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?

Offers one concrete use case ('to learn the exact tool names and argument fields pipeline conditions test'), which implies when to reach for it. However, it names no alternatives, no when-not-to-use, and no prerequisites, leaving the routing decision to inference.

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