NanoParse MCP

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

With no annotations provided, the description carries the behavioral disclosure burden. It candidly discloses the payment model, the error condition, the retry mechanism, and cross-client compatibility without custom headers. It does not detail every possible failure mode, but the core behavioral profile is well communicated.

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 description is compact, front-loaded with the tool's purpose, and every clause earns its place. The payment workflow is conveyed in one efficient sentence without redundancy.

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?

Given the simple parameter surface, the existence of an output schema, and the detailed payment guidance, the description is largely complete for an agent to invoke the tool correctly. It could briefly note what Litmus is, but the output schema likely covers that return-value detail.

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 input schema covers both parameters at 100%, so the baseline is 3. The description adds valuable context for payment_signature by explaining when it is needed, where the terms come from, and how to retry, going beyond the schema's standalone description.

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 clearly states the tool fetches a URL and returns clean Markdown enriched with Litmus scoring, which is a specific verb and resource. It does not explicitly contrast itself with the sibling nanoparse_status, though its function is obviously distinct from a status-checking tool.

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 description provides clear operational guidance: free tier limits, per-request pricing, and the exact retry flow when payment_required is returned. It does not explicitly say when to prefer this tool over nanoparse_status, but the fetch-vs-status distinction is strongly implied.

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

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

With no annotations provided, the description carries the behavioral burden. It discloses that this is a check-only operation and that it returns actionable funding guidance. It does not explicitly state side-effect-free behavior or quota consumption details, but 'status' and 'Check' strongly imply read-only semantics.

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 tight sentences with no filler. The first sentence states the tool's scope, and the second gives immediate actionable guidance. Every sentence earns its place.

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 simple one-parameter status tool with an output schema, the description covers purpose, usage timing, and decision value. It could mention potential edge cases like invalid addresses, but nothing essential appears missing for the agent to call it correctly.

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 already fully describes the single 'address' parameter with 100% coverage. The description adds no new parameter-level detail beyond what the schema provides, so the baseline score of 3 is appropriate.

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 ('Check') and concrete resources: wallet balance, USDC balance, quota state, and next-call success. It clearly differentiates itself from the sibling nanoparse_fetch by framing this as the pre-flight status check rather than the action itself.

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?

'Use before spending' gives explicit timing guidance and tells the agent to call this before funding. It does not explicitly state when not to use it or contrast it with nanoparse_fetch, so it just misses the top score.

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