status

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without description help. The description adds genuine behavioral context by naming the categories of data returned (transport, endpoints, schema origin, event subscription), but it does not say whether this performs live probing of the provider, whether results are cached, or what the cost/latency profile is.

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 sentence, front-loaded with the core purpose ('How this MCP server is connected') before the field enumeration. Every clause carries information, though the trailing 'provider's own health and info' is the one piece that muddies rather than clarifies, since it collides with sibling tool names.

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 zero-parameter, read-only diagnostic tool with no output schema, the description usefully enumerates what is returned, standing in for the missing output documentation. The remaining gap is routing: it does not establish its relationship to the 'health' and 'info' siblings it overlaps with, which matters for selection on a server with ~60 tools.

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, so the baseline is 4 — there is no parameter semantics to explain. Schema coverage is 100% and the empty object schema with additionalProperties:false is self-explanatory.

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 names a clear subject — how the MCP server is connected — and enumerates the concrete fields returned: transport, endpoints, schema provenance, event subscription, provider health/info. That is well beyond a tautology of the name 'status'. However, it does not distinguish itself from the sibling tools 'health' and 'info', whose territory it explicitly claims, so an agent cannot tell the three apart from this text alone.

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 statement of when to call this tool versus alternatives, and no prerequisites or exclusions. The gap is compounded by siblings named 'health' and 'info' that appear to overlap directly with the provider health/info portion of this description, and nothing here disambiguates them.

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