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

With no annotations provided, the description carries the burden of behavioral disclosure. The verb 'check' implies a read-only operation, but the description does not explicitly state that there are no side effects, nor does it mention any rate limits, data freshness, or other behavioral traits. It is an implied safe read, but not fully transparent.

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 sentence that is concise and front-loaded with the verb and resource. It states the scope (10 jurisdictions, 12-trap defenses) without fluff, making it efficient and easy 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?

Without an output schema, the description should clarify what the agent will receive, but it does not. It only states the action and scope, not the return format or content. For a status-check tool, an agent needs to know if it gets a list, a summary, or a pass/fail. This is a significant gap.

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 schema provides complete coverage (100%). The description does not need to explain parameter meaning since none exist. The baseline of 4 for no parameters is appropriate; the description adds no conflicting information.

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 the verb 'Check' with a specific resource ('current regulatory monitoring status') and scopes it to '10 jurisdictions and 12-trap defenses', making the tool's purpose clear. It distinguishes itself from siblings like verify_mineral_lot_compliance (specific lot) and list_trade_precedents (historical listings) by focusing on current status.

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 guidance on when to use this tool versus alternatives. No exclusions, prerequisites, or conditions are mentioned. The description does not hint at what problem it solves relative to sibling tools, leaving the agent to infer usage context.

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 of behavioral disclosure. The verb 'Query' implies a read operation, and listing the embedded precedents gives content context, but the description does not disclose the return format, pagination, or any limitations, leaving the agent guessing at output shape.

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 well-formed sentence that front-loads the verb and resource and packs the enumerated precedents efficiently. Each element earns its place, though listing four full case citations adds length without much extra decision value.

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 0-parameter list tool this is reasonably complete, but with no output schema and no annotations, the description should clarify what the returned data looks like (e.g., case summaries, citation lists, rulings). That gap leaves the agent uncertain about the call's 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?

There are zero parameters, so the schema offers nothing to document. The description compensates by naming exactly what the tool returns access to (the four precedents), which is the meaningful semantic content an agent needs. Baseline 4 is appropriate for a parameterless tool.

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 ('Query') and resource ('international trade jurisprudence precedents embedded in the oracle'), then enumerates the exact precedents available (WTO DS592, WTO DS431, ICSID ARB/15/31, US CIT Superior Wire). This clearly distinguishes it from the compliance-verification and feedback 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 description conveys its purpose and content scope, so an agent can infer it is for retrieving precedent case law, but it never explicitly states when to use it versus alternatives, nor does it name exclusions or routing conditions to sibling tools like verify_mineral_lot_compliance.

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 must carry behavioral context. It clearly implies a read-only list operation with no side effects, but it does not disclose what 'active' means, pagination behavior, error handling, or what fields are returned. For a simple list tool this is borderline adequate, but additional clarity would help.

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 no wasted words. It states the action and resource directly, though it could benefit from a brief mention of usage or parameters.

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 list tool with two optional parameters and no output schema, the description is minimally sufficient but lacks details like the meaning of 'active', return format, or any filtering nuances. It does not actively mislead, but leaves room for interpretation.

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 already documents both parameters (limit and mineral_focus) with descriptions, so schema coverage is 100%. The tool description adds no extra meaning or context about how these parameters behave or interact, so it does not improve beyond the schema baseline.

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 clear action (List) and resource (active autonomous agent evolution proposals and improvement requests), making it distinct from siblings like verify_mineral_lot_compliance or list_trade_precedents. It does not explicitly name alternatives, but the resource is specific enough to avoid confusion.

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 guidance is given on when to use this tool versus siblings. There is no mention of alternatives, prerequisites, or context where this tool is the right choice, leaving the agent to infer from the name.

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 full burden of behavioral disclosure. It states the tool submits feedback, but does not disclose side effects (e.g., whether submission persists, if it triggers review, idempotency, rate limits, or auth requirements). For a write operation with zero annotation coverage, this is a significant 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?

The description is a single, well-structured sentence that front-loads the purpose and lists the main use cases. It is concise with no fluff, though it could be slightly shorter without losing meaning. It earns a 4 for efficient delivery.

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 tool has 8 parameters (3 required) and no output schema, the description provides a high-level purpose but does not mention expected return values, submission confirmation, or any side effects. The schema covers parameter details, and the description covers the intent, but for a submission tool with no annotations, one might expect more context on what happens after submission. It is adequate but not 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?

Schema description coverage is 100%, so the schema already documents all 8 parameters, including enums with descriptions. The description mentions 'evolution proposal, mineral dataset addition request, regulatory edge case, or protocol improvement,' which loosely maps to the feedback_type enum but adds little beyond what the schema already states. Baseline 3 is appropriate since 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 clearly states the tool's purpose: an agent or operator submits evolution proposals, dataset additions, edge cases, or protocol improvements to evolve the Minerals Oracle engine. It uses a specific verb (submit) and resource (feedback to the engine), and the listed types distinguish it from sibling read/check tools like verify_mineral_lot_compliance or list_trade_precedents.

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 usage for submitting improvement ideas, but it does not explicitly state when to use this tool versus alternatives or provide any exclusions. There is no mention of sibling tools like minerals_list_evolution_proposals (which likely lists existing proposals) or when not to submit. Usage context is clear enough, but no alternative routing is provided.

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, and it does so by disclosing the concrete evaluation logic: concession geofencing, CEEC barcode seal validation, ASM co-mingling segregation, ILO 138/182 checks, RMI RMAP certification, and mass-balance tolerance (<=2.5% loss). It does not, however, disclose failure modes, permissions, or what the result conveys, so it stops short of full transparency.

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 is front-loaded in the first clause, followed by a compact enumeration of checks. It is jargon-dense and one long sentence, which slightly hurts readability, but essentially every clause corresponds to a distinct validation the agent should expect.

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 18-parameter, no-output-schema tool, the description covers what is evaluated well but never indicates the return shape (pass/fail, findings, scores) or how a non-compliant lot is reported. Given there is no output schema, that outcome context is a real gap.

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 89%, so the schema already documents the parameters (baseline 3). The description adds genuine semantic context by tying parameters to evaluation logic, e.g. geofencing maps to coordinates/concession, FEOC equity cap to feoc_equity_pct, and the ~23.5t:1t ratio to the ore/hydroxide mass-balance inputs.

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 precise verb and resource (verifies DRC Katanga heterogenite-to-cobalt hydroxide supply-chain provenance) and enumerates the exact domain checks performed. It is unmistakably distinct from the cobalt-adjacent siblings such as verify_lithium_origin, verify_nickel_origin, and verify_mineral_lot_compliance.

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 tight domain scoping (DRC Katanga cobalt hydroxide), so an agent can infer it is the cobalt-specific verifier. However, it never states when to prefer this over verify_mineral_lot_compliance or the other verify_* siblings, nor any 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 full burden, and it does disclose substantial behavior: it writes a Master Passport on Polygon (an on-chain write with implicit irreversibility), enforces 'zero FEOC taint', and cryptographically binds proofs into a Merkle Root EIP-712 signature. It omits auth/permission needs, cost, and failure modes, which is why it falls short of 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?

The purpose and outcome are front-loaded in the first clause, followed by the compliance regimes it enforces. It is a dense single run-on sentence heavy with stacked jargon and semicolons, but every clause carries a distinct regulatory/technical fact, so little 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 a high-complexity, multi-nested-object tool with no annotations and no output schema, the description covers the domain well: it names the regimes (IRA 30D, EU Battery Regulation 2023/1542, CSDDD), the outputs (Master Passport, Merkle Root EIP-712 signature), and the streams. It stops short of describing the return payload structure or error conditions, which an output-less tool could have benefited from.

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 six parameters (including the nested origin-verify payloads and defaults); baseline is 3. The description only loosely maps to the three mineral lot parameters via 'Orchestrates Australian Lithium, Indonesian Nickel, and DRC Cobalt streams' and adds no format or constraint detail beyond the schema.

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 opens with a precise verb+resource ('Evaluates end-to-end composite EV battery pack compliance and issues a Master Passport on Polygon') and the keyword 'composite'/'end-to-end' clearly distinguishes it from the single-mineral siblings (verify_lithium_origin, verify_nickel_origin, verify_cobalt_origin). An agent can tell this is the aggregating multi-stream tool without opening any 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 text describes capabilities but never states when to choose this tool over verify_mineral_lot_compliance or the per-mineral verify tools, nor any prerequisite ordering (e.g. lots must be verified first). No exclusions or conditions are given, so the agent must infer routing from the word 'composite' 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 full disclosure burden. It does add real value by revealing the evaluation logic and thresholds (SC6.0 to LiOH <= 2.5% loss, FEOC cap < 25% clean origin), but it says nothing about read-vs-write behavior, what a failure result looks like, or whether a verification is recorded or stateful. Some behavioral substance, significant gaps remain.

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 that front-loads the verification target before the evaluation criteria. No filler, though the stacked acronyms (SC6.0, IRA 30D, FEOC) compress a lot into one line.

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, 6-required tool with no annotations and no output schema, the description covers the domain well but omits what the verification returns, how pass/fail is signaled, and when the optional MINEDEX ID is needed. An agent would still need to probe the response shape.

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 83%, so the schema already documents nearly all parameters with examples and defaults. The description adds no parameter-level syntax or format detail beyond what the schema provides, so the baseline 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 (verifies) and a tightly scoped resource (Australian hard-rock spodumene to lithium hydroxide provenance), then enumerates the three concrete checks it runs (MINEDEX geofencing, stoichiometric mass balance, IRA 30D FEOC origin). This scope clearly separates it from siblings like verify_nickel_origin, verify_cobalt_origin, and verify_mineral_lot_compliance.

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 explains what is evaluated but never states when to reach for this tool versus the sibling verification tools, nor any prerequisites (e.g., that MINEDEX tenement ID is optional, or that AU-origin lots are required). Usage must be inferred entirely from the domain naming.

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 of disclosing behavioral traits. It transparently notes that outputs are algorithmic heuristics derived from satellite/market data and explicitly cautions against treating them as official or certified. This goes beyond a bare description, though it does not detail side effects, errors, or rate limits, which would be expected in an ideal case.

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 exactly two sentences: the first states the purpose, the second delivers a critical caveat. Every word earns its place, and the most important information (purpose) is front-loaded. There is no redundancy or 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?

Given the tool's complexity (12-trap rules, five parameters, no output schema), the description is relatively brief. It explains what it computes but does not describe the output format, how results should be interpreted, or how the parameters interact. The caveat is helpful but does not compensate for the lack of return-value guidance, which would be essential for an agent to correctly use 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 description coverage is 60% (three parameters have descriptions, two have enums without descriptions). The description adds context about the purpose of the parameters ('open satellite/market data' and 'regulatory rule heuristics') but does not provide per-parameter semantics beyond what the schema already offers. This meets the baseline but does not elevate it.

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 a specific verb ('fetches' and 'computes') applied to a defined resource ('raw algorithmic indices' and '12-trap regulatory rule heuristics'), making the tool's purpose unambiguous. It also implies a distinction from siblings like get_compliance_status and list_trade_precedents by focusing on algorithmic heuristics rather than status or precedents.

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 a critical usage warning ('DO NOT use as an official regulatory legal filing or physical assay certification without independent manual verification'), which is useful, but it does not explicitly state when to prefer this tool over its siblings (e.g., 'use for screening, not for final decisions'). The caveat implies a secondary role but lacks direct guidance on selection.

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 it does disclose meaningful behavioral context: the evaluated jurisdictions (IMIP Morowali, IWIP Weda Bay), the regulatory thresholds applied (25% FEOC cap, 2.5% mass-balance loss), and CBAM screening. However, it never states whether the operation is read-only, what a pass/fail result looks like, or how non-compliant inputs are handled.

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 densely packed sentence that front-loads the resource and then lists the five evaluation axes in parallel structure. Every clause corresponds to a distinct check, though the heavy jargon density makes it less scannable than a bulleted breakdown would be.

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 13-parameter compliance tool with no annotations and no output schema, the description covers the evaluation scope well but omits the return shape and outcome semantics, which the agent must infer entirely. Adequate but with a clear gap given zero structured support.

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 92%, so baseline is 3, but the description adds real interpretive value beyond the schema by defining the ~31t Limonite to 1t MHP stoichiometric ratio and the 2.5% loss tolerance that govern limonite_ore_input_tons/mhp_output_tons, and the FEOC 25% equity ceiling that governs feoc_equity_pct.

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 (verifies) and a precisely scoped resource (Indonesian laterite Limonite-to-Nickel MHP supply-chain provenance), then enumerates the exact checks performed. This clearly separates it from siblings like verify_lithium_origin, verify_cobalt_origin, and verify_composite_battery_passport without needing to name them.

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 nickel/MHP specificity tells an agent to pick this over the lithium or cobalt verifiers. There is no explicit when-to-use statement, no mention of prerequisites (e.g. that a SIMBARA NTPN and HPAL refinery must be known first), and no when-not guidance.

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