Get Mcp Compliance Status

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds useful behavioral context beyond that: it enumerates the four categories of information returned, which matters because there is no output schema. It does not say whether results are a live probe or static config, which is the one remaining gap.

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 short sentences, with the purpose front-loaded and the return contents following. The opening clause largely restates the tool name, but the second sentence earns its place by listing the reported facets; there is no filler.

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 tool with no output schema, the description covers both what the tool does and the shape of what comes back. The only missing element is whether the status reflects live server state or stored configuration, which would help an agent interpret the result.

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 schema has zero properties and explicitly forbids additional properties, so there is nothing for the description to disambiguate. Baseline 4 applies for a parameterless tool; nothing in the text misleads about inputs.

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 specific verb and resource (get MCP 2026-07-28 specification compliance status) and enumerates the concrete facets returned: batching status, protocol version, header validation, migration guidance. Sibling tools like get_mode or get_global_config cover different resources, so confusion is unlikely, though the description never explicitly contrasts itself with them.

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 explicit statement of when to call this tool, when not to, or which sibling to use instead (for example get_global_config or get_registry_info for adjacent configuration reads). The only guidance is implied by the word 'compliance status'; the agent must infer the trigger condition, such as pre-migration verification.

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