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

With no annotations provided, the description carries the behavioral burden and discloses important traits: it reads stored data rather than probing the network, and missing or stale observations are returned as unknown. It does not cover authentication requirements or rate limits, but for a read-only lookup tool the key behavioral distinction is well communicated.

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 description is two tight sentences with no wasted wording. The primary purpose and scope are front-loaded, followed immediately by the key behavioral caveat about unknown results and no network probe.

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 tool with no output schema and no annotations, the description covers purpose, scope, and key return behavior for missing or stale data. It could go further in describing the health snapshot structure, but it gives enough context for correct invocation.

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 0%, so the description must compensate. It explains both parameters semantically: resourceType is 'agent or MCP server' and name is the 'exact catalog name.' This maps directly to the required inputs and clarifies lookup precision, though it does not add format examples beyond the schema.

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 (Read), resource (latest stored reachability and protocol health snapshot), and scope (for an agent or MCP server by exact catalog name). It also explicitly distinguishes this tool from a network probe, which helps an agent select it correctly against related lookup tools.

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?

It clearly indicates when to use the tool: to read the latest stored health snapshot by exact catalog name. It also provides a key boundary condition, stating that missing or stale observations return unknown and that the tool does not trigger a network probe. It does not name a specific alternative for live probing, so it is not a full 5.

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