freedom_structured_extractor

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

With no annotations, the description carries the full behavioral burden, and it does disclose a meaningful trait: the tool is paywalled behind HTTP 402 (L402/x402) at a stated price. However, it says nothing about rate limits, error behavior, or what happens if payment proof is missing/invalid, which matters for a payment-gated tool.

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 extraction capability is front-loaded, which is good, but the definition is padded with promotional noise ('85 Sats / ~$0.080 USDC | 100/100 SLA Guaranteed', 'Live BTC Oracle'). Pricing and payment gating do earn their place; the SLA slogan does not.

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?

There is no output schema, so the description must convey what comes back, and it does list the return contents (JSON rows, headings, links, financial figures, BTC context) plus the payment prerequisite. It is fairly complete for a read-only extractor, with only error/auth-failure behavior left unaddressed.

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 100%, so all three parameters (url, text, authHeader) are already documented in the schema, and the description adds no syntax or format detail beyond it. Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific verbs and resources: extracting HTML tables into JSON rows, headings, hyperlinks, financial figures/tickers, and BTC price context. An agent can tell it does structured extraction, though it never explicitly differentiates itself from the sibling freedom_clean_scraper. The heavy marketing framing ('Live BTC Oracle') clutters rather than sharpens the purpose.

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 when-to-use or when-not-to-use guidance, and no sibling is named as an alternative despite freedom_clean_scraper and freedom_python_sandbox existing. The only selection hint ('if no URL is provided') lives in the schema, not the description. An agent gets no routing help from the text.

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