PHION Enrichment

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 two useful behavioral traits: the assessment is bounded by supplied evidence, and the call costs 0.005 USDC (a paid operation). It does not disclose what happens when evidence is insufficient, what the signed receipt guarantees, or any permission/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?

A single dense sentence with no filler, and the core purpose plus the output contents and price are front-loaded. It is appropriately sized for the amount of information offered, though it packs the price tag on with a semicolon in a slightly awkward way.

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?

An output schema exists, so return values need not be described, but for a tool with three parameters, nested objects, and 0% schema coverage the definition is materially incomplete. It gives no indication of what must go into 'subject' or what qualifies as valid 'evidence', which an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters including two nested objects, so the description must compensate but does not. It never mentions 'subject', 'signals', or 'evidence' directly, leaving the agent to infer the shape of the required subject object and the maxItems=32 evidence array from the raw schema alone.

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 operation (evidence-bounded reputation assessment) on a specific resource (an agent subject), and lists what the result contains (confidence, coverage, provenance limitations, signed receipt). It is clearly distinguishable from generic siblings like verify or attest, though it never names a sibling to differentiate against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The phrase 'evidence-bounded' weakly implies evidence must be supplied, but nothing tells the agent which of the many sibling preflight/verify/screening tools to prefer in a given situation.

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 does add meaningful context by disclosing a free input preflight, provider attribution, signed evidence, and a fixed price of 0.005 USDC, which helps an agent understand billing and validation behavior. However, it omits broader operational details such as authentication requirements, data source behavior, failure modes, and return structure, so it is only partially 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 dense sentence with no filler: it names the operation, key features, and cost. The information is packed tightly, though it slightly sacrifices clarity by relying on jargon like 'provider attribution' without elaboration.

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 28 parameters, nested objects, no output schema, and no annotations, the description is too thin to support correct invocation. It provides no invocation guidance, no examples, no explanation of what the signed evidence contains, and no comparison to similar enrichment tools. An agent needing to choose parameters or interpret the result would be under-informed.

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 7%, and the tool description itself adds no parameter-level meaning beyond 'company enrichment.' The schema's own description does clarify that identifier can be pdl_id, website/domain, profile, ticker, name, company, or identifier and that nested inputs are accepted, but the remaining ~26 parameters are opaque. The description does not compensate for the low 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 identifies a clear domain ('Company enrichment') and distinguishes it from sibling evidence tools such as contact_enrichment_evidence, person_enrichment_evidence, and entity_enrichment_evidence by naming the company scope. It does not state what the returned 'signed evidence' contains, which leaves some ambiguity about the tool's exact output, but the primary purpose is recognizable.

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 gives no explicit guidance on when to use this tool versus sibling alternatives like contact_enrichment_evidence or entity_enrichment_evidence. There are no exclusion criteria, no mention of alternatives, and no condition-based routing. The only implicit signal is that it is for company-related enrichment.

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 useful behavioral traits: free input preflight, identity limitations, signed receipt, and the 0.007 USDC cost. But it omits whether the operation is read-only, what the signed receipt contains, and possible failure modes.

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 tight sentence, front-loading the core purpose and packing cost, preflight, and identity constraints without filler. It could be slightly better structured, but it earns its brevity.

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 28 parameters, no output schema, and no annotations, one line is insufficient. An agent cannot determine which identifier to pass, what the signed receipt looks like, or how identity limitations affect the enrichment 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 only 7%, yet the description names no parameters and gives no guidance on the 28 inputs. It only implies the input is a business contact, which does little to clarify how to populate fields like lid, pdl_id, query, or subject.

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 'Business-contact enrichment' – a specific verb and resource – and the 'business-contact' qualifier helps distinguish it from company or person enrichment siblings. However, it does not name any sibling or explicitly state what the evidence output looks like.

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 usage context or alternatives are provided. The description mentions preflight and identity limitations but never says when to use this tool over company_enrichment_evidence, person_enrichment_evidence, or entity_enrichment_evidence.

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 bears the full burden of behavioral transparency. It adds some useful traits—source-bounded results, explicit missing facts, and a 0.008 USDC cost—but it does not disclose read/write behavior, whether it fetches the source URLs, persistence, auth, response shape, or failure semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is compact and front-loaded: scope appears first, missing-facts behavior second, and price last. There is no filler and each clause earns its place. It is under-specified overall, but the structural efficiency is strong.

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 three parameters, a nested subject object, no output schema, and a crowded sibling list, the one-sentence description is insufficient. The agent cannot learn how evidence is returned, how subject relates to expected_fields, or when to select this tool over similar ones.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage for three parameters, so the description must compensate. It indirectly maps 'source-bounded' to source_urls, 'entity' to subject, and 'field coverage ... missing facts' to expected_fields, adding some meaning beyond the bare schema names. However, it does not explain formats, requiredness, constraints, or how subject and expected_fields interact.

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 conveys a specific output concept—'Source-bounded entity field coverage with explicit missing facts'—and mentions the price, but it uses a noun phrase rather than a clear verb+resource statement. It does not distinguish this from siblings like multi_source_fact_bundle or source_backed_search.

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 exclusions, and no reference to alternatives. The description only characterizes the result and cost, leaving the agent to infer when this evidence tool should be chosen over the many related tools in the sibling 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?

Annotations declare readOnlyHint=true and destructiveHint=false, but the description says successful inspections cost 0.009 USDC and failed inspections are not charged. Charging a fee is a side effect that contradicts the read-only annotation, so the description contradicts the structured behavioral hints.

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 front-loaded sentence with three semicolon-separated clauses; every clause adds distinct information: scope, failure billing, and price. There is no wasted wording.

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 does not explain what the inspection checks, what constitutes a failed inspection, or what result is returned. For a paid pre-payment inspection, this leaves the agent without enough context to interpret the outcome.

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 0% and the lone 'url' parameter has no schema description. The protocol list weakly suggests the URL is an agent endpoint in one of those protocols, but it does not explain what URL should point to or what forms are accepted.

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: pre-payment agent inspection across named protocols. It is clear enough to distinguish from generic tools, though it does not explicitly differentiate itself from siblings such as payment_preflight or counterparty_risk_preflight.

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 'Pre-payment' implies use before paying an agent, but there is no explicit when/when-not guidance or mention of alternatives such as payment_preflight, try_service, or verify. The agent must infer timing from the title-like clause rather than from stated usage rules.

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 behavioral transparency burden. It does add useful details: free input preflight, provider attribution, likelihood, limitations, signed receipt, and a price of 0.006 USDC. However, it does not disclose authentication needs, side effects, rate limits, or what the returned evidence/receipt structurally contains.

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 with no filler words, and it front-loads the core purpose before listing notable features and cost. It is appropriately brief, though the semicolon-joined feature list reads a bit densely.

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?

The tool has 28 parameters, no output schema, and no annotations, so the description is severely insufficient. It does not explain how to construct a valid request, what fields are meaningful together, what the signed receipt looks like, or how preflight and validation behave. An agent would be guessing on most operational details.

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 7% across 28 parameters, and the tool description does not compensate. It mentions 'person' and 'free input' but does not explain any of the parameters, their roles, required combinations, or how the service interprets them. The description adds almost no semantic value over the sparse 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 identifies a specific action and resource: 'Person enrichment'. It also distinguishes itself from sibling enrichment tools like company_enrichment_evidence and contact_enrichment_evidence by naming 'person' as the subject. However, the phrase is somewhat jargon-heavy and doesn't fully explain what 'enrichment evidence' means in practice.

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 about when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or conditions that would route an agent to a different sibling tool. The only implicit hint is the word 'person', which is not enough for a tool with so many siblings.

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?

Annotations already cover idempotency, read-only, open-world, and destructiveness, and the description adds real context beyond them: budget enforcement, persistent idempotency, acceptance-criteria evaluation, a signed completion envelope as output, and the absence of a gateway surcharge. It stops short of describing failure behavior or what a rejected acceptance check yields.

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 densely packed sentences with no filler; the core pipeline (gate, execute, evaluate, return) is front-loaded and the pricing note is a useful trailing clarification.

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 mutating, open-world, 7-parameter tool with no output schema and 0% parameter documentation, the description covers the return concept ('signed completion envelope') but omits dry_run semantics, failure modes, and rejection behavior. Adequate but with clear gaps.

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 0%, so the description must carry meaning, and it hints at max_budget_atomic ('enforce a budget'), idempotency_key ('persistent idempotency'), acceptance_criteria, and target_service. However, objective, input, and dry_run go entirely unaddressed, so it only partially compensates for the coverage gap.

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 ('execute') plus resource ('one selected PHION service') and frames the tool as a gateway with budget/idempotency/acceptance gating. It is distinguishable from most siblings, though it never names the closest alternatives such as try_service or preflight.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not guidance. The word 'universal' and the gateway framing imply broad applicability, but an agent cannot tell from the text when to pick phion_execute over try_service, preflight, or transaction_assurance.

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 disclosure burden, and it discloses almost nothing beyond 'free' — no auth requirements, no explanation of what makes a URL unsafe, no behavior on failure, and no rate limits. Calling something a safety check without saying what it inspects or returns leaves real ambiguity.

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 front-loaded sentence with no filler; the core action leads. It is efficient, though the terseness edges toward under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with no output schema, the description still omits what a 'safety' verdict consists of and what the caller gets back, which is the main thing an agent needs to decide whether to gate a downstream action on 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 0% for the single required url parameter, and the description only says a URL is checked. It does not clarify expected form (absolute? scheme? relative paths rejected?), which matters because the schema only declares format: uri with no 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?

The description gives a concrete verb-plus-resource framing: it checks a URL for safety and reachability. That is enough for an agent to know what it does, but it never distinguishes itself from the sibling payment_preflight, which sounds nearly identical in kind.

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 payment_preflight, verify, or the other siblings, and no prerequisites (e.g., authenticate first, call before payment). The agent is left to infer the workflow position of a 'preflight' entirely 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?

With no annotations, the description carries the full burden; it does disclose genuine behavior beyond the schema: free tier, rate limiting, non-mutation of payment-critical values. But it omits error/invalid-payload behavior, what the rate limit actually is, and whether normalization mutates or returns a new payload.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the key guarantee front-loaded after the purpose clause; no filler. Slightly dense with unattributed modifiers ('Free, rate-limited') but appropriately sized.

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, with a nested free-form payload object and an undocumented required target_service string. An agent cannot reliably construct a valid invocation from this description alone; payload shape, service identifiers, and failure behavior are all missing.

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 0%: the nested 'payload' object has no field documentation, and 'target_service' is never mentioned in the description at all, so its expected values are entirely unknown. The description adds some intent ('payment-critical values are never changed') but does not compensate for the uncovered, required parameters.

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 action pair (validation and safe key normalization) on a specific resource (payload) with scope (before payment). The adjectival 'Free, rate-limited' implicitly distinguishes it from the sibling schema_normalize, but the distinction is left for the agent to infer rather than stated.

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?

Gives a clear timing context ('before payment'), which implies when to reach for it, but never names the alternative schema_normalize or states when to use the paid variant instead. No exclusions or prerequisites are given.

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 full responsibility for behavioral disclosure. It does mention 'identity limitations' and a cost of 0.006 USDC, but it does not state whether the operation mutates state, requires authentication, has rate limits, or what outcomes an agent should expect.

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 text is short but reads as a noun-phrase fragment rather than a usable definition. It front-loads no actionable information, and the cost/limitation details are appended without explanation, so brevity comes at the expense of substance.

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 three parameters, a nested object, no output schema, and dozens of sibling tools, this description is far too sparse. An agent cannot determine how to construct a valid request, what response to expect, or how this tool fits among its alternatives.

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 0% and the description does not mention query, subject, or source_urls. The required source_urls parameter is undocumented, and the nested subject object is entirely unexplained, so the agent cannot infer parameter semantics from either source.

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 identifies the tool's domain (public social-source observations) and mentions attribution and identity limitations, but it lacks a verb stating what the tool actually does – e.g., fetch, verify, or record evidence. Without that, an agent cannot determine how it differs from siblings like fetch_evidence, source_backed_search, or onchain_evidence.

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 rather than the many evidence-related siblings. The only contextual clue is the 0.006 USDC price, which implies a paid operation, but no selection criteria, prerequisites, or exclusion conditions 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. It discloses that the operation is free and requires no wallet, suggesting a non-mutating informational action. However, it does not explicitly state that it does not execute the service, only that it gives a 'preview', and it omits any potential side effects or error behavior. The transparency is decent but not exhaustive.

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 that covers the essential points: free, representative preview, exact price, upgrade instructions, and no wallet requirement. Every phrase adds value, with zero wasted words. It is ideal for quick agent comprehension.

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?

The tool has one parameter with a large enum, no output schema, and no annotations. The description explains what it returns (preview, price, upgrade instructions) and that it targets paid services. It does not mention error handling or output format, but given the informational nature, it is largely sufficient for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, so the description must add meaning. It clarifies that the 'service' parameter selects a paid service from the enum. However, it does not elaborate on what each enum value represents or how to choose between them. Given the long list of services, this is a minimal but helpful clarification.

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 purpose: providing a free preview, exact price, and upgrade instructions for any PHION paid service. It explicitly notes that no wallet is required, distinguishing it from tools that execute actual paid transactions. The verb 'provide' and resource 'preview, price, upgrade instructions' make the action specific.

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 does not provide explicit guidance on when to use this tool versus the many service-specific siblings (e.g., payment_preflight, attest). It implies generic applicability ('any PHION paid service') but lacks a clear 'use this when...' or 'use that instead...' instruction, leaving the agent to infer the appropriate choice.

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 only discloses that verification is 'Free' (a genuine cost signal), but says nothing about whether it is read-only, what permissions it needs, what a failed verification looks like, or what the tool returns.

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 filler. It is efficient, though arguably under-specified rather than truly concise given the gaps elsewhere.

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 three parameters, nested objects, 0% schema coverage, no output schema, and no annotations, one sentence is insufficient. An agent lacks guidance on what 'content' and 'sources' are for and how to interpret a verification 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 0% for three parameters, and the description only implicitly touches the 'receipt' parameter. The 'content' and 'sources' parameters (the latter an array, the former unexplained) receive no meaning at all, leaving most inputs undocumented.

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: 'verification of a PHION signed receipt.' An agent can tell this is a verification tool, not an attestation or payment tool. However, it offers no differentiation from the sibling 'journey_verify,' which also sounds like a verification operation, and the 'PHION' term is opaque without domain context.

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 use this tool versus alternatives like journey_verify, attest, or preflight, and no prerequisites or exclusions. The only usage-adjacent signal is 'Free,' which hints at cost but not routing.

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