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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description's job is to add beyond that, and it does: OAuth account:read consent, an unmetered read, no mutation of prices/inventory/orders/publication/config, and a 'Shared MCP Baseline 1.0.0' envelope carrying scope, provenance, unknowns, omissions and typed errors. The value is partially diluted by irrelevant carry-over clauses about expired cursors, foreign/deleted targets and provider failures that do not apply to a zero-argument, zero-cursor call.

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 useful signal (what is inspected, consent requirement, read-only/unmetered, envelope shape) is buried among sentences that do not apply: expired cursors, unavailable stores, foreign or deleted targets, provider failures. It reads as a generic compliance template rather than a front-loaded description of one specific call.

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?

An output schema exists, so return values need not be spelled out, and annotations cover the safety profile, leaving consent and non-mutation as the genuine gaps, which are filled. Still, the description never clarifies its relationship to sibling introspection tools, which is the main thing an agent needs in this crowded toolset.

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?

With zero parameters and 100% schema coverage, the baseline is 4 and there is no parameter semantics to add. The instruction 'Supply only the fields in its strict input schema' is slightly confusing for a tool whose schema has no fields, but it does not mislead 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 first sentence names a specific verb plus the concrete resources inspected: authenticated principal, granted scopes, store access, versions and environment. That is far more informative than the title, but it never distinguishes this from close siblings such as supercatch_get_capabilities or supercatch_get_connection_health, so an agent must guess which of the three introspection tools to pick.

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 contextual guidance (requires OAuth account:read consent, does not grant access, is read-only and unmetered), which implies when it is appropriate. However, the one routing sentence, 'Use supercatch_get_context for this read in the connected account,' is circular and no alternative or exclusion is named despite many overlapping sibling tools.

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