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

Goes beyond the annotations by disclosing the auth scope requirement, the absence of network/LLM access, and a retry policy ("fresh attemptId for each intended call; never automatically retry an uncertain result") that the schema's attemptId description only partly covers. The one unexplained tension is readOnlyHint=false on what is described as a pure "free deterministic computation" — the description never says what non-read-only side effect (metering/ledger) that hint implies.

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?

Front-loaded with what the tool does and its hard limits, then cost/determinism, then auth, then retry policy — each sentence carries distinct information. It is dense (three clauses packed into the first sentence) but no sentence is 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?

With no output schema, the description still never indicates what a call returns (a boolean, a validity verdict, a list of schema violations) or how failures are surfaced — the central question for a validation tool. Coverage of limits, auth and retry is good, but the return-shape gap leaves the definition incomplete for its complexity.

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 50% (only attemptId is documented in-schema), and the description reinforces attemptId semantics (fresh ID per call, do not retry) but says nothing about the structure of the required `input` object — that it must contain `schema` and `value` must be inferred from the tool name. Baseline 3 fits: some added value, but the undocumented half of the parameters is not fully compensated.

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+resource ("JSON Schema validation") and immediately bounds the capability: "bounded structural subset; no code, regex, references, composition or network." That scope statement distinguishes it implicitly from sibling validators/converters like invokeport_json_types and invokeport_json_repair, though those siblings are never named.

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 exclusions ("no code, regex, references, composition or network") effectively tell the agent when this tool will not suffice, and the auth note ("Requires a scoped key allowing json-schema") is a precondition an agent must know. It stops short of routing to an alternative sibling when the subset is too narrow, so it is clear context rather than explicit when/when-not/alternatives.

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