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

No annotations exist, so the description carries the full burden. It does disclose the pricing/metering model and subscription exemption, which is genuinely useful, but says nothing about whether the call is read-only or state-changing, expected latency for a 'full matrix', failure/partial-result behavior, or what the response contains — a large gap for an unannotated, potentially expensive operation.

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 with the verb front-loaded, and the parentheticals carry real information (endpoint mapping, pricing). Dense but no filler; slightly overloaded by stacking operation mapping and billing in one clause.

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 annotations, no output schema, and 0% parameter coverage including a nested object, the description must do much more than it does. It covers purpose and cost but omits return shape, error behavior, and the meaning of four of five inputs.

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 coverage is 0% across 5 parameters, including a nested server_config object and an enum idp_shape. The description only gestures at 'client x IdP-shape' and 'full', leaving apply_shims, server_config, and the format of the clients array entries entirely undefined, and it is ambiguous whether 'full' implies the full_matrix flag.

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?

States a specific verb and resource: 'run one full client x IdP-shape conformance matrix', and anchors it to a concrete backend operation (POST /check). That is distinct enough from the billing/account siblings (claim_trial, subscribe_solo, subscription_status) and run_history, though it never names them explicitly.

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?

The cost clause ('$0.01 per check unless your account has an active Solo subscription/trial') implies the agent should verify entitlement via subscription_status or claim_trial first, but that routing is left to inference. There is no explicit when-to-use/when-not-to-use statement or named alternative.

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