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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, covering the safety profile. The description adds no behavioral context beyond that: no indication of whether results are static reference data or live-discovered, nor any hint about the shape or size of what comes back. The openWorldHint is especially unelaborated.

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?

A single, front-loaded sentence with no filler. It is terse to the point of being a fragment, but nothing is wasted.

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 parameters, rich safety annotations and no output schema, the description still should say what a caller receives (transport names? code snippets? compatibility matrix?) since no structured field covers the return value. It stops at naming the topic, leaving the agent to discover the output empirically.

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?

The tool takes zero parameters and schema coverage is 100%, so there is nothing for the description to compensate for. Baseline 4 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 verb 'Find' plus the objects 'supported transports, clients and connection guidance' conveys the rough domain, but 'connections' is never defined and the description never distinguishes this tool from other discovery-oriented siblings such as read_agent_manifest, read_engines or read_site_policy. An agent would have to guess whether this is about network transports, MCP client compatibility, or configuration guidance.

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 statement, no prerequisites, and no named alternative among the many read_* siblings. The only implicit cue is the 'read_' prefix, which the agent already gets from the name.

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