x402 Agent Hub

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the paid x402 flow ($0.01 USDC on Base), and crucially discloses a coverage limitation — the buy→sell round-trip simulation only runs on six of the eight chains, with no simulation mentioned for Avalanche or Solana. It does not state latency, rate limits, or whether a failed simulation yields partial results, which keeps it below a 5.

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 sentences, front-loaded with the action and its scope, and the second sentence adds a genuinely distinct capability rather than repeating the first. The chain enumeration is long but earns its place given the parameter enum; a slightly tighter phrasing could have listed the simulation-supported chains once.

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 tool with no output schema and four parameters, the description effectively previews the report contents by enumerating every audited dimension, which is what an agent needs to judge relevance. The main gap is that it doesn't distinguish paid vs free paths or indicate what a partial/failed audit looks like.

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 the baseline is 3 and the schema already explains chain defaulting, address formats, and the default order size. The description adds only modest value, explaining that intendedOrderUsd drives AMM slippage estimation, but it says nothing about paymentSignature or what happens if payment is omitted.

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?

Specific verb (audit) plus resource (token contract) with an explicit enumeration of the checks performed: honeypots, taxes, hidden ownership, whale concentration, LP locks, liquidity depth, slippage. The supported chain list is spelled out, so an agent knows exactly the scope without opening the schema. Clearly differentiated from generic lookups like chain_token_info.

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?

Usage is implied by how specific the checks are — you reach for this when you need safety/due-diligence analysis rather than a plain balance or metadata lookup. However, it never says when NOT to use it or names an alternative sibling (e.g. chain_token_info) for simpler needs, and it doesn't state prerequisites such as needing a funded payment for x402.

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, the description carries the full burden; it does add useful context: a fixed price of $0.02 USDC on Base and that results are instant. However, it does not explain whether payment is required up front, how the x402 flow works, or what triggers the optional paymentSignature, leaving key behavior undisclosed.

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 front-loaded sentence with no wasted words; pricing is appended where it belongs, at the end.

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 two-parameter audit tool with no output schema, the description conveys the output shape (0-100 score plus prioritized fixes), latency, and cost. The only missing piece is the mechanics of the payment requirement.

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 both url and paymentSignature are already documented. The description adds no constraints or format hints for either parameter, so the baseline of 3 applies.

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: an instant 0-100 Technical SEO & Website Modernization Audit scorecard with prioritized fixes. The resource domain (website SEO) is clearly distinguishable from sibling tools like audit_crypto_token or calculate_prop_firm_risk.

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?

Usage is only implied: an agent can infer this is the tool for auditing a website's technical SEO. There is no explicit when-to-use/when-not guidance, no prerequisites (e.g., payment setup), and no alternatives are named.

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, the description carries the full burden. It does disclose two important traits: the tool is paid ($0.01 USDC on Base, corroborated by the paymentSignature parameter) and its output reflects drawdown auto-lock status. It does not say whether the call is read-only/pure computation, what happens when no payment signature is supplied, or how errors surface.

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 dense sentence with the core operation front-loaded and no filler. It compresses several concepts into one line, which borders on over-packing but nothing is wasted.

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 an 8-parameter, no-annotation, no-output-schema tool, the description covers the domain and the payment requirement but leaves return content (lot size units, lock-status format) and two parameter meanings unstated. Adequate to start, not sufficient to call confidently.

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 75%, so the schema documents most parameters and the baseline is 3. The description adds conceptual context (spread/commission friction, drawdown limits) but does not clarify the two undocumented drawdown-limit parameters or how riskPercent and currentEquityUsd interact with accountBalanceUsd.

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 ('Calculate exact CFD/Forex lot size') and adds differentiating qualifiers (ECN spread/commission friction, prop-firm drawdown auto-lock). An agent can tell this apart from get_cfd_microstructure or get_ict_sessions. It does not name siblings, but the operation is distinct enough.

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?

No statement of when to use this tool versus alternatives, no prerequisites (e.g. must have account balance and stop distance), and no exclusions. The prop-firm framing implies a use case but the agent must infer it. There is also no guidance that this call costs $0.01 USDC.

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, the description carries the full burden and does disclose real behavior: a per-call price of $0.003 USDC on Base and a settlement rule that invalid input, not-found and upstream errors are not charged. It omits rate limits, latency, and what a 'not-found' response looks like, but the payment/auth behavior is unusually well covered.

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 sentences, front-loaded with the verb and scope, with no filler. The parenthetical proxy-standard catalogue is dense but each entry (EIP-1967, ZeppelinOS/USDC, EIP-1167) is materially useful to an agent deciding whether this tool detects a given proxy pattern.

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 describe return values, and it does by listing the classification fields it produces. Combined with the chain coverage and payment terms, an agent has enough to decide and call correctly; only the shape/format of the actual response is left implicit.

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 chain, address, and paymentSignature are already fully documented, including the chain list and defaults. The description adds only the count of supported chains and the payment context, not new per-parameter semantics, so the baseline 3 applies.

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 ('Classify') and resource ('any address on 7 EVM chains') and enumerates exactly what is returned: EOA vs EIP-7702-delegated vs contract, code size, nonce, native balance, and named proxy standards. This cleanly separates it from siblings like chain_native_balance or chain_token_info, which return a single facet rather than a full address classification.

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?

'before interacting with it' gives a concrete decision context for when to reach for this tool, and the pricing/settlement sentence tells the agent the cost of a failed call. However, it never names an alternative (e.g., use chain_native_balance for balance-only reads) nor states when not to use it, so routing is implied rather than explicit.

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, the description carries the full burden and does well: it discloses the resolver path (Ethereum mainnet Universal Resolver), CCIP-read/offchain support, and the payment model ('only pay for successful reads', $0.002 USDC on Base). It does not describe return shape or rate limits, but covers key behavioral traits beyond the schema.

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 two compact sentences with the core action and constraint front-loaded. The parenthetical and payment note are useful and not redundant.

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 no output schema and no annotations, the description supplies resolver context, mutually exclusive parameters, and settlement behavior. It omits the exact return format, but for a simple resolution call the essential invocation details are present.

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 100%, so the baseline is 3, but the description adds a meaningful constraint not encoded in the schema: exactly one of 'name' or 'address' must be supplied. The paymentSignature parameter is documented only in the schema, which is acceptable given full schema coverage.

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 states a precise verb ('Resolve') and resource ('ENS name to an address, or an address to its primary ENS name') and names the resolver mechanism. This clearly distinguishes it from generic address tools like chain_address_info.

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?

It gives explicit input selection guidance: 'Pass exactly one of name or address.' It does not name alternative sibling tools or state when reverse resolution is preferable, but the usage condition is unambiguous for calling it.

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, the description carries the burden and adds useful behavior: return shape includes raw wei, formatted units, and the block number, and settlement only occurs on successful reads. It does not cover auth or rate-limit behavior, but the pricing and error-cancellation semantics are valuable disclosure.

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 purpose and supported chains are front-loaded, followed by return contents and payment terms in one dense but useful sentence. It is appropriately sized, though the pricing parenthesis is slightly separated from the core description.

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 read-only balance lookup with no output schema, the description explains what is returned (raw wei, formatted units, block) and the payment model. It is nearly complete, with only minor gaps around failure modes beyond settlement cancellation.

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 chain, address, and paymentSignature are already documented. The description reinforces chain coverage and address scope but adds little syntax or format detail beyond the schema, making the baseline 3 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?

States a specific verb-equivalent operation and resource: reads native coin balance for any address across named chains. The word 'native' distinguishes it from sibling chain_token_balance, so an agent can select correctly without inspecting the schema.

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?

Clear context is given: use for native coin balances on supported chains, and the accepted chains are listed. It does not explicitly name alternatives such as chain_token_balance or state when not to use this tool, so it stops short of full routing guidance.

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, the description carries the full burden and does so: it discloses partial-failure handling (failed chains appear in chainsFailed), settlement behavior (only successful reads are charged; invalid input, not-found and upstream errors cancel settlement), and the exact price ($0.005 USDC on Base). This is exactly the payment and error semantics an agent needs before invoking.

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?

Three dense sentences, front-loaded with the payoff (one call vs 21) and then failure and pricing semantics; almost nothing is wasted. The closing parenthetical price could arguably be folded in earlier, keeping it from a 5.

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?

No output schema exists, and the description compensates by stating what comes back (per-chain native/USDC/USDT balances, a total stablecoin figure, and chainsFailed). Combined with the payment semantics, an agent has everything needed to call it and interpret the result.

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 already 100%, so the baseline is 3; the description adds meaning by clarifying that chains accepts a subset with all seven as default and by tying paymentSignature to the settlement behavior described above. It does not add syntax detail beyond the schema example, so it stays below 5.

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 gives a specific verb and resource — returns native coin, USDC and USDT balances across seven named chains plus a total stablecoin USD figure — and explicitly frames it as a batch replacement for 21 separate reads, which differentiates it from the sibling single-chain tools (chain_native_balance, chain_token_balance).

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?

'Instead of 21 separate reads' clearly signals when to prefer this over the per-chain siblings, and the 'or a chains subset' phrasing tells the agent how to narrow scope when full coverage isn't needed. It stops short of naming the alternative tools explicitly or stating exclusions, so it is not a 5.

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, the description carries the full load and does well: it discloses the pay-per-call billing model ($0.002 USDC on Base), that settlement only occurs on successful reads while invalid input/not-found/upstream errors cancel it, and that output includes both raw and decimal values plus the symbol. It omits anything about auth/payment-signature requirements (left to schema) and latency or rate limits.

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: capability and scope first, then the mis-scaling rationale, then billing terms. Every clause carries information an agent or caller needs, and nothing is buried.

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?

No output schema exists, but the description still characterizes the return value (raw + decimal-formatted + symbol) and the error/billing behavior, which is the critical unknown for a paid read. It stops short of describing the error response shape or what happens for a non-contract token address.

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 four parameters are already documented, including the chain list and 0x-prefix requirements. The description adds only the count of supported chains ("7"), which duplicates rather than extends the schema; baseline 3 applies.

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 ("ERC-20 token balance of any address") plus scope (7 EVM chains) and return shape. The "ERC-20" qualifier implicitly distinguishes it from chain_native_balance and chain_token_info, so an agent can pick it without opening another schema.

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?

Usage is implied by "any address on 7 EVM chains" and the pricing note, but it never says when to prefer this over siblings like chain_native_balance (native coin) or chain_portfolio (multi-asset). No exclusions or prerequisites are stated.

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, the description carries the full burden and does real work: it discloses that this is a paid call ($0.002 USDC on Base), that settlement is cancelled on invalid input, not-found, and upstream errors, and that reads are effectively non-destructive. It stops short of stating rate limits, required auth/identity for x402, or latency characteristics.

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: the capability and returned fields come first, the pricing and settlement terms second. Nothing is redundant and no sentence could be dropped without losing signal.

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?

No output schema exists, but the description compensates by naming the returned fields, and the paid-call/failure-billing semantics are disclosed, which is the main behavioral risk for this tool. Minor gaps remain around error shape and what happens when the payment signature is absent versus supplied.

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 the schema already documents chain, token, and paymentSignature in detail, including the default chain and accepted chain names. The description adds only the count of supported chains, which is marginal value over the schema rather than new parameter meaning.

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 resource (ERC-20 token metadata) with the exact fields returned (name, symbol, decimals, formatted total supply) and the scope of 7 EVM chains. This clearly separates it from siblings like chain_token_balance and chain_address_info, which cover different resource types.

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?

Usage is only implied by the resource described: an agent can infer this is the metadata lookup rather than a balance or address lookup. There is no explicit when-to-use, when-not-to-use, or named alternative, and no prerequisites for the payment flow beyond the pricing line.

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, the description carries the full burden. It discloses the return fields, the payment model ('you only pay for successful reads: invalid input, not-found and upstream errors cancel settlement'), and the cost ($0.002 USDC on Base). It does not cover rate limits or explicitly state read-only status, leaving some behavioral gaps.

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 two sentences, front-loaded with the core purpose and followed by a precise use case and payment terms. Every sentence earns its place with no waste.

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 no output schema, the description lists the key return fields (status, confirmations, block time, from/to, value, fee) and explains the payment model. It is nearly complete, though it could clarify the paymentSignature parameter's role and any authentication requirements.

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 the schema already documents all three parameters fully. The description adds only marginal context by mentioning '7 EVM chains' and specific chains, which is already in the schema; it does not add meaning beyond what the schema provides.

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 and resource (transaction status) and enumerates the returned fields (pending/success/reverted, confirmations, block time, from/to, value, all-in fee) across 7 EVM chains. It does not explicitly differentiate itself from sibling chain_* tools, so it stops short of a 5.

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?

It states a clear use case: 'Use it to confirm a payment or deployment landed.' However, it does not mention when not to use it or name any alternative sibling tool, so it lacks exclusions.

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 full burden and adds useful behavioral context: it specifies that only successful reads are charged, errors cancel settlement, and it names the returned fields such as filing/report dates and direct links. It still omits some operational details like rate limits or pagination, but it meaningfully goes beyond the schema.

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 two tight sentences with no wasted text. It front-loads the core resource and then adds payment behavior, making it easy for an agent to parse quickly.

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 rich schema coverage and absence of an output schema, the description does a good job stating what the tool returns and how payment/settlement works. It is nearly complete, though it could explicitly clarify ticker versus CIK and how the tool relates to sibling company-data tools.

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 six parameters are already documented in the input schema. The description reinforces that form type and date are optional filters, but does not add syntax or format details beyond what the schema already provides.

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 identifies the resource as a company's most recent SEC filings and mentions the optional form/date filters. It is specific enough for an agent to understand what the tool returns, but it does not explicitly distinguish this tool from siblings such as company_financials or company_insider_trades.

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 implies this tool is for SEC filings and notes that form type and date can be used as optional filters. However, it gives no explicit when-to-use guidance, no exclusions, and no comparison to related tools like company_insider_trades or company_financials.

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, the description carries the full burden and does well: it discloses that Q4 and quarterly cash flows are derived from YTD filings and flagged, and it explains the payment model (only successful reads settle; invalid input, not-found and upstream errors cancel). It does not describe the response shape, which is the main remaining gap.

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 sentences, front-loaded with the resource and covered metrics, then the caveats and billing. Dense but every clause carries information; the metric enumeration is long but justifies itself for a fundamentals tool.

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?

No output schema and no annotations mean the description must do heavy lifting, and it covers data source, metrics, period controls, derivation caveats and payment behavior. Only the shape of the returned records (field names, nesting) is left unexplained.

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 the parameters are already documented at baseline. The description reinforces period granularity (annual/quarterly, 1-12 periods) but adds no syntax or format detail beyond the schema, so a 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 concrete resource (reported fundamentals from SEC XBRL) and enumerates the exact metric set and period scope, so an agent can immediately tell this is not the filings or profile tool. It lacks an explicit contrast sentence naming siblings like company_filings or company_profile, which keeps it from a 5.

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?

Usage is implied by the metric list and the annual/quarterly plus 1-12 period scope, but there is no explicit 'use this when you need X instead of company_filings/company_profile' guidance. The ticker-or-CIK alternative appears only in the schema, not the description.

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, the description carries the full burden and does disclose non-obvious behavior: settlement only occurs on successful reads, while invalid input, not-found, and upstream errors cancel settlement, plus the exact price ($0.005 USDC on Base). It omits read-only framing and rate limits, but the payment/error semantics are unusually well specified.

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 return fields are front-loaded in a single dense sentence, and the payment terms are isolated in a compact second sentence. It is information-dense with minimal waste, though the parenthetical field list is slightly long.

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 compensates by enumerating the returned fields (insider, role, code, shares, price, value, holdings, 10b5-1 flag, summary). Combined with fully documented schema parameters, an agent has enough to call it correctly; only explicit pagination behavior is left implicit.

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 ticker, cik, limit, and paymentSignature are already documented. The description adds no parameter-specific nuance beyond the schema, making the baseline 3 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 resource and content type (parsed SEC Form 4 insider filings for a company) and enumerates the fields returned, so an agent knows exactly what data it gets. It does not explicitly contrast itself with the sibling company_filings tool, which keeps it from a 5.

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 statement of when to call this versus company_filings, company_financials, or company_profile, and no prerequisites are mentioned. The only selection hint ('Provide ticker or cik') is already in the schema.

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 at all, the description has to carry the full behavioral load, and it does disclose the most consequential non-obvious trait: the metered payment model, the price ($0.002 USDC on Base), and that failed/nonexistent reads cancel settlement. That is real value beyond the schema. It stops short of saying anything about rate limits, latency, or whether invalid-input cancellation is automatic or requires a signature.

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 returns, then a compact billing caveat, then the price. The long field enumeration is not padding — it substitutes for the absent output schema — so every clause carries information.

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?

Full parameter coverage, no output schema, and no annotations, so the description correctly fills the return-shape gap by listing the payload fields, and it covers the payment model. Remaining gaps are minor: error behavior beyond 'settlement is cancelled' and any freshness/caching characteristics of the SEC data are not stated.

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 cik, ticker, and paymentSignature are already documented in structured form. The description adds marginal meaning — that payment is only settled on success, which contextualizes paymentSignature — but gives no syntax or format detail beyond the schema. A baseline 3 fits.

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 resource (official SEC profile of a US public company) and enumerates exactly which fields come back — legal name, tickers, exchanges, SIC, incorporation state, fiscal year end, website, address, former names, report links. That enumeration makes it clearly distinct from siblings such as company_filings, company_financials, and company_insider_trades.

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?

Usage is only implied: the schema says 'Provide ticker or cik', so an agent can infer this is the entry point for looking up a company from either identifier. But there is no explicit guidance on when to call company_profile versus company_search or company_filings, and no statement of prerequisites or exclusions.

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, the description carries the burden and does substantial work: it discloses a concrete price ($0.002 USDC on Base), the settlement rule that only successful reads are charged, and that invalid input, not-found and upstream errors cancel payment. That is exactly the kind of cost/auth context an agent needs. It still omits rate limits, pagination behavior beyond the limit param, and latency/retry expectations.

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?

Three tight sentences: what it searches, why you'd call it, then cost/settlement terms. Front-loaded with the capability and zero filler; the parenthetical pricing sits at the end where it belongs.

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?

No output schema exists, and the description compensates by naming the exact return fields (ticker, legal name, CIK). Payment is covered thoroughly. The remaining gap is result-set behavior — ordering, whether limit caps at 25 with no offset, and what a zero-result response looks like — for a 3-parameter tool this is minor.

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 q, limit and paymentSignature are already documented in the schema; baseline is 3. The description reinforces that matching is on ticker or name but adds no syntax, normalization, or partial-match rules, and never mentions paymentSignature at all despite describing the payment model in prose.

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 (search), a precisely bounded resource (~10,000 SEC-registered US public companies), match keys (ticker or name), and the fields returned (ticker, legal name, CIK). The closing clause positions it as the lookup step feeding the other company_* siblings, so an agent can tell it apart from company_profile or company_filings.

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 phrase 'to use with the other company tools' gives clear context: call this first to resolve a ticker/CIK, then hand that identifier to the other company endpoints. It stops short of explicitly naming which sibling to call next or when not to use this tool, so it is strong context rather than full routing guidance.

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, the description carries the full behavioral burden. It usefully discloses cost ($0.015 USDC on Base) and filtering logic (rejects office PSTN landlines, detects phantom wa.me/linktr.ee links), which is real value. However it omits whether the call fails without paymentSignature, whether charging happens per-call or per-success, and any latency/rate/failure behavior for what is clearly a paid external enrichment 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?

A single front-loaded sentence that opens with the verb and purpose before piling on the capability list; no filler or restatement of the name. Slight deduction because the pricing clause is grafted onto the end of the capability list, blurring extraction scope with billing terms.

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 must convey what comes back, and it does so indirectly by listing the extracted entities. But it never describes the response shape (per-field nulls, confidence, partial results on failure) or the payment flow prerequisites, which matters for a paid three-parameter tool with no annotations.

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 the schema already documents url, businessName, and paymentSignature fully, establishing a baseline of 3. The description adds only marginal semantic color — 'sanitize brand names' loosely maps to businessName and the USDC price hints at paymentSignature — without explaining accepted formats or how payment signatures interact with the charge.

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 (enrich) and resource (business URL/lead) and then enumerates the concrete outputs: brand sanitization, phantom link detection, E.164 phone extraction, emails/socials, and CMS/analytics pixel detection. This is unmistakably distinct from siblings like generate_outreach_dossier or extract_clean_markdown.

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 phrase 'for SDR/sales outreach' implies the context of use, but there is no explicit when-to-use/when-not guidance and no reference to a sibling alternative (e.g. generate_outreach_dossier, which likely consumes this output). The agent must infer selection from the description alone.

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, the description carries the burden well: it discloses the payment model ($0.003 USDC on Base), the settlement rule (only successful reads charge; invalid input, not-found and upstream errors cancel), and enumerates the returned data domains. It still omits auth/paymentSignature requirements and any latency or multi-match behavior.

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 the verb and scope, followed by the return coverage and then pricing. The long field enumeration is dense but each item is a genuine capability claim; only the parenthetical currency note could be trimmed.

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 4-param lookup tool with no output schema and no annotations, the description covers input keys, output breadth and cost behavior — the essentials an agent needs to decide and pay. The main residual gap is disambiguation against near-identical company_* and entity_* siblings.

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 the schema already documents id, name, domain and paymentSignature. The description restates the three lookup keys but adds no precedence rule (e.g. whether id wins over name and domain) or format detail beyond what the schema provides. Baseline 3 applies.

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?

Specific verb (Enrich) plus resource (company) with explicit scope qualifiers — private, startup or listed, worldwide, not just US — and three accepted identifiers. It is clearly distinguishable in domain from chain_* or audit_* siblings, though it never explicitly contrasts with the very close company_profile / company_search / entity_search siblings.

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 scope note ('not just US', covers private and listed) implies when this is the right enrichment tool, and the three identifier styles hint at call strategies. But there is no explicit when-to-use versus company_profile, company_search, entity_search or enrich_business_lead, and no when-not guidance or prerequisites.

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, the description does substantial work: it identifies Wikidata and Wikipedia as sources, states that this is a paid read, explains that invalid input, not-found, and upstream errors cancel settlement, and lists exclusions. It still does not cover rate limits or explicit error-response behavior beyond settlement cancellation.

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 front-loaded and organized into three functional parts: purpose and returned fields, explicit exclusions, and payment behavior. It is efficient overall, though the long colon-delimited field list is somewhat dense.

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?

Because there is no output schema, it is important that the description enumerates returned fields, exclusions, sources, and payment behavior, and it does so. The remaining gap is that it does not clarify how to choose between id and name or what happens when neither is supplied, despite zero required parameters.

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%, and the schema already documents id, name, and paymentSignature. The description adds no parameter-specific meaning beyond the schema, 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 opening names the resource clearly: a professional profile of a notable person, with examples of person types and an explicit list of returned fields. It does not explicitly distinguish itself from sibling tools like entity_search or entity_company, so sibling differentiation is left to inference.

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?

It gives implied usage context by scoping the tool to founders, executives, and public figures, and it warns that family, residence, and full birth dates are not returned. However, it does not name an alternative tool or give explicit when-to-use versus when-not-to-use guidance.

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, the description carries the burden and does meaningful work: it discloses pricing ($0.002 USDC on Base) and the settlement policy (invalid input, not-found and upstream errors cancel settlement). It omits auth mechanics beyond the schema's paymentSignature field and says nothing about rate limits or result ordering.

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 sentences, front-loaded with the action and payload, followed by the payment/settlement term. Every clause earns its place and nothing is padded.

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?

No output schema exists, and the description compensates by stating what comes back (IDs, short descriptions, Wikipedia links) plus failure-cost behavior. Pricing and payment are covered; only edge behavior such as empty-result handling or result ranking is 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 the schema already documents all four parameters including defaults and the 1-20 limit range. The description only reinforces that `q` is a name and hints at the entity classes; it adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

Names a specific verb+resource ("Search Wikidata ... by name") and enumerates the return payload (IDs, short descriptions, Wikipedia links). It positions itself relative to the enrichment step, but never disambiguates from the sibling `company_search`, which plausibly does the same thing for one entity class.

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?

"so you can pick the right entity before enriching it" gives a clear usage context and sequencing hint toward `entity_company`/`entity_person`. No explicit when-not conditions or named alternatives, so it stops short of full routing guidance.

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?

No annotations exist, so the description carries the full burden. It usefully discloses the cost and payment rail ($0.005 USDC on Base, x402), but says nothing about failure modes: paywalled/JS-rendered pages, timeouts, rate limits, or what happens when payment is missing or invalid.

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?

One dense sentence that front-loads the action, the resource, and the output contract, with the pricing caveat last. No 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 does name the return payload (Markdown, metadata, token count), which is good. But for a paid x402 endpoint the payment flow is the riskiest part of invocation and is left unexplained, and nothing covers behavior on unfetchable pages.

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 100%, so baseline is 3; the description adds real meaning by explaining the monetary cost behind the paymentSignature parameter and the economic rationale for maxChars ("token-efficient"). It still doesn't explain the payment handshake (e.g., whether an unpaid call returns a 402 challenge).

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 concrete verb chain (fetch a public webpage, convert to Markdown) plus the output qualities (metadata, token count). Sibling tools are unrelated domains, so no differentiation is needed, but it also doesn't explicitly bound itself against any other fetch/convert capability.

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?

"Any public webpage" implies the only stated precondition (publicly reachable, non-authenticated pages), but there is no explicit when-to-use, when-not-to-use, or alternative guidance. The agent must infer that this is for turning web content into LLM-consumable text.

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, the description carries the full burden. It does disclose the important behavioral facts that this is a paid call ($0.05 USDC on Base) and that it bundles many analyses, which is genuinely useful. However, it does not explain the payment gating behavior — that omitting paymentSignature likely yields a payment challenge, or whether an unsigned call runs at all — nor any latency, rate limit, or side-effect profile.

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 verb and resource are front-loaded, which is good, but the remainder is a single dense marketing sentence packed with branded jargon ('Brand Sanitizer', 'Phantom Lead Shield') that an agent cannot act on. Some listed components double as a useful output preview, so the length is not pure waste, but it is closer to a sales pitch than a specification.

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; the component list does serve as a rough return-value preview (contacts, SEO audit, scripts), which partially covers that gap. What is missing is the payment flow contract and any indication of output format or size for a tool that claims to produce a full dossier.

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 the four parameters are already documented, and the baseline is 3. The description adds marginal value only by tying the stated $0.05 USDC price to the paymentSignature parameter; it says nothing about how url, businessName, or agencyOffer shape the output beyond what the schema already states.

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 and artifact ('Generate a complete B2B SDR Outreach Dossier in 1 call') and enumerates the bundled components, so an agent knows this is an all-in-one bundle rather than a single narrowly scoped analysis. It implicitly distinguishes itself from narrower siblings like audit_technical_seo or enrich_business_lead by the 'in 1 call' framing, but never names those siblings 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 'in 1 call' phrasing implies the usage case (choose this instead of chaining several focused tools), which is useful but never stated as an explicit rule. There is no guidance on preconditions, such as what happens when the target URL is not a real business site or when the payment signature is omitted.

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?

No annotations are provided, so the description must carry the full behavioral burden. It mentions a cost ('$0.01 USDC on Base') and live data, but does not explain payment requirements, whether reads are safe, rate limits, or what happens if paymentSignature is omitted.

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 a single front-loaded sentence with dense but relevant information. It avoids repetition and clearly leads with the primary action, though the long metric list makes it somewhat hard to parse.

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 complex market-data tool with no annotations and no output schema, the description covers the metrics and symbol universe but leaves gaps around payment flow, optional-parameter behavior, and output structure. It is adequate but not fully complete for correct invocation.

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 the schema already documents both optional parameters. The description adds context by listing supported symbols and the USDC payment cost, but does not add syntax or clarify default behavior when symbol is omitted.

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, 'Get', and a detailed resource: institutional ECN spreads, commissions, ATR, execution cost ratios, scalping suitability, and live MT5 FVGs for a listed set of symbols. It is very clear what the tool returns, though it does not explicitly differentiate itself from the sibling get_ict_sessions.

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 lists what data is returned and for which symbols, but gives no explicit guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites. Usage is only implied by the metric list.

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?

No annotations are provided, so the description carries the burden. It usefully discloses cost ('FREE ($0.00)') and freshness ('live'), and 'Inspect' implies a read-only operation. However, it does not mention authentication, rate limits, or explicitly confirm no side effects, leaving some behavioral gaps.

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 efficiently packed sentence, front-loaded with the key cost signal followed by the scope of what is inspected. Every phrase contributes specific information without waste.

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 and no annotations, the description does a good job enumerating what the catalog returns (tickers, per-call pricing, OpenAPI URL). It stops short of describing the response format or structure, but for a simple zero-param inspection tool it is nearly complete.

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 tool has zero parameters, so the baseline score of 4 applies. There are no parameter semantics to clarify in the 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 states a specific verb 'Inspect' and a precise resource 'live x402 Agent Hub service catalog', then enumerates its contents (tickers, pricing, OpenAPI URL). It is clearly distinct from the audit/calculate/render siblings, though it does not explicitly name or contrast any sibling.

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?

Usage is implied by 'Inspect the live... catalog' – an agent can infer this is a discovery tool – but there is no explicit when-to-use, when-not-to-use, or alternative routing guidance (e.g., 'call this first to discover services before using other tools').

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, the description carries the full disclosure burden. It does add one genuinely useful behavioral fact not in the schema: the call costs $0.005 USDC on Base (the schema only names a paymentSignature field, not that payment is metered or what happens on an unpaid call). Beyond that it is silent on read-only semantics, whether an unpaid request returns a 402 challenge, error behavior, or data freshness/latency for 'live' values.

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 dense sentence with the core payload front-loaded and zero filler. It is jargon-heavy (FVG, Silver Bullet, triple-swap) but each term names a distinct data product rather than restating the name.

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 and no annotations, the description does the minimum: it lists the categories of data returned. It does not describe the response shape, timestamp/timezone formatting, whether all four categories are always present, or the payment flow. Adequate to decide whether to call, but not to call it confidently.

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 the schema already explains both `at` (ISO-8601 UTC, defaults to now) and `paymentSignature`. The description reinforces the live-default behavior but adds no format, range, or historical-lookup semantics beyond what the schema states. Baseline 3 applies.

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 uses a specific verb ('Get') and then enumerates the exact resources returned: ICT Killzones by session name, 60m Silver Bullet FVG windows, CFD rollover spread alerts, and triple-swap flags. An agent knows precisely what data it gets. It does not differentiate itself from the adjacent sibling get_cfd_microstructure, which likely overlaps on spread/rollover content, so it stops short of a 5.

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 when-to-use guidance, no statement of preconditions, and no naming of alternatives or exclusions. Nothing tells the agent when to prefer this over get_cfd_microstructure or calculate_prop_firm_risk, nor when a historical 'at' lookup is appropriate versus the live default.

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, the description carries the full burden and discloses important traits: deterministic output, typo-free rendering, SVG + data URI return format, and a $0.025 USDC on Base cost. It stops short of explaining payment mechanics, error behavior, or whether payment is optional, so it is strong but not complete.

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 definition is a single front-loaded sentence with no filler. It is dense but well-structured, packing the main output types and cost into one statement; only minor parsing strain from the long parenthetical.

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 12-parameter paid rendering tool with no annotations and no output schema, the description is too thin. It clarifies output format and cost but omits most parameter semantics, payment flow details, and error or return-value expectations that an agent would need to invoke it confidently.

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 only 17% for 12 parameters, so the description must compensate but does not. It names the three templates and implies sparkline usage and payment cost, but leaves badge, theme, subtitle, brandName, accentColor, metricDelta, metricLabel, metricValue, and paymentSignature unexplained.

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 uses a specific verb (render) and precisely names the resource (OpenGraph banner, social KPI slide, trading signal sparkline card) with dimensions and output format (SVG + data URI). An agent can immediately understand what the tool produces without opening the schema.

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 three card types imply when the tool might be used, but there is no explicit guidance on when to use this versus alternatives or when not to use it. The description leaves usage selection to inference from the template names.

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