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

With no annotations, the description carries the disclosure burden and does so well: it states the tool never signs, never moves funds, requires SERANOX_API_KEY (staked account, utility #10), and returns both unsigned transaction and fee quote. This prevents the dangerous assumption that calling it executes a trade.

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 sentences, front-loaded with action and output, followed by the two most decision-relevant caveats (no signing, auth requirement). No redundant 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?

For a tool with no annotations and no output schema, the description covers the core safety and output facts: unsigned transaction, fee quote, and API key requirement. It leaves the agent without a full return-field map or explicit note on optional slippage behavior, but those are inferable from the schema.

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?

Description adds no parameter-level information; it only describes the operation. The schema already documents pair and amountIn, while side is obvious from its enum and slippageBps has default/bounds but no prose. Coverage is moderate (50%), so this is acceptable but not exemplary.

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 ('Builds a memecoin swap through the Seranox router') and the key output ('UNSIGNED transaction plus a fee quote'), making it distinct from the list/status/risk siblings. The title confirms the unsigned nature.

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 clear operational context: it returns an unsigned transaction and explicitly says 'never signs and never moves funds,' directing the agent to hand `unsignedTx` to a wallet. It lacks a named alternative for execution/signing, so it stops short of explicit when-to-use-this-versus-X 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 provided, the description carries the full behavioral burden. It notably discloses that the tool is read-only, does not route equities, and burns 1 SERA, which is valuable cost and side-effect information. It does not mention pagination, default scope when ticker is omitted, or rate limits, but the core behaviors are 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 compact and front-loaded with the key metrics, followed by two short sentences that convey critical behavioral constraints. Every sentence earns its place with no filler or repeated 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?

For a tool with one optional parameter and no output schema, the description covers the main return categories and the important side effect of burning 1 SERA. It would be more complete if it stated what happens when `ticker` is omitted, but the core information an agent needs to invoke and interpret the tool is 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 description coverage is 100%, so the single optional `ticker` parameter is already documented as a filter. The description adds context about the output metrics, but does not add new meaning to the parameter itself beyond what the schema provides. A baseline 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 clearly identifies the tool as providing tokenized equities dislocation metrics: on-chain print vs last exchange close spread, 24h net flow, and accumulator/distributor classification. It lacks an explicit verb like 'get' or 'list', but the resource and data points are specific enough to distinguish it from routing and wallet tools.

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 context by stating 'Read-only by design — Seranox does not route equities,' which tells an agent this is not for execution. However, it does not explicitly name alternatives like seranox_build_route for routing or seranox_get_pair for standard pair data, so the guidance remains implicit 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explicitly states 'Burns 1 SERA', which is a critical cost side effect. It also promises 'Full detail' as the return behavior. It does not mention error handling or other potential side effects, but for a read-like operation with a fee, this is sufficient.

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 concise sentences, front-loading the primary purpose and then disclosing the fee. Every word earns its place; no fluff or redundant phrasing.

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 single-parameter tool with no output schema and no annotations, the description covers the core aspects: what it does, how to identify the pair, and the cost. It does not detail the return structure, but 'full detail' implies comprehensive data. Missing explicit guidance on error cases is a minor gap, but overall it is adequate for an agent to call it correctly.

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

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

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying the accepted formats: 'id, symbol (e.g. WKND or $WKND), or contract address', including a concrete example of symbol notation. This goes beyond the schema's terse 'Pair id, symbol, or address.' and helps the agent format the input correctly.

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 action: retrieving full detail for a single pair, identified by id, symbol, or contract address. It clearly distinguishes itself from siblings like seranox_list_pairs (which lists all pairs) and seranox_risk_scan (which scans risks). The verb 'get' and resource 'pair' are precise, and the input formats are specified.

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: when you need full detail for a specific pair rather than a list or other operations. It does not explicitly state when not to use it or name alternatives, but the context 'Full detail for one pair' is clear enough for an agent to infer the right scenario.

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 disclosure, and it does: it warns that the tool 'Burns 1 SERA' and that 'Sponsored slots are labeled.' These are non-obvious costs and content policies an agent needs before invoking. It does not discuss rate limits or error behavior, but the disclosed facts are meaningful.

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

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

The description is compact and all three sentences earn their place: the first defines the result set and fields, the second flags sponsored content, and the third states the cost. No filler or redundant restatement of the tool 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?

For a tool with no output schema and no annotations, the description does a good job: it lists expected output fields, risk categories, sponsored-slot behavior, and the SERA burn. It does not explicitly say it returns an array, but the schema and phrasing make that inferable, and the parameter docs fill most remaining 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 75%, so the schema already explains risk, sort, and maxAgeMin. The description adds little beyond what the schema provides, though it does reinforce the risk verdict values. Baseline 3 is appropriate because the schema carries most of the parameter burden.

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 resource ('new memecoin pairs on Robinhood Chain') and the data returned, which makes the tool's purpose clear. It does not explicitly differentiate itself from siblings like seranox_get_pair or seranox_risk_scan, but the resource and field list make it recognizable as a list/discovery tool.

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

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

It implies usage: an agent needing newly listed memecoin pairs with risk verdicts would use this tool. However, there is no explicit guidance on when not to use it, nor any mention of alternatives such as seranox_get_pair for a single pair or seranox_risk_scan for deep risk analysis.

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?

The description discloses the 'Burns 1 SERA' cost, a key behavioral side effect, and enumerates the output fields. However, it does not explicitly state read-only status or other potential side effects, relying on the absence of annotations.

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 concise sentences: the first lists the output fields, the second states the cost. Information is front-loaded and there is no redundancy.

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

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

While the description lists output fields and the cost, it omits the filtering capability (tag parameter) and the limit parameter's behavior, which are present in the schema but not explained. Given no output schema, the description should have clarified these aspects for a complete understanding.

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 50% – only 'tag' is described, while 'limit' lacks a description. The tool description does not compensate by explaining the limit parameter or the filtering behavior, so agents may not understand how to use these parameters effectively.

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 lists tracked wallets and enumerates the specific data fields returned (labels, tags, 30d PnL, win rate, etc.), making its purpose unambiguous and distinct from sibling tools like seranox_list_pairs or seranox_get_pair.

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 listing tracked wallets but does not explicitly contrast with alternatives or state when not to use it. The context is clear, but there is no exclusion or alternative 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 behavioral disclosure burden. It does disclose a meaningful side effect/cost: the scan burns 5 SERA. It also lists the checks performed, which helps the agent anticipate the scan's scope. It does not describe the verdict format, but the key behavioral trait (cost/burn) is 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?

Two dense sentences carry the entire value: the first enumerates what is checked and the second states the per-scan cost. There is no filler, repetition, or boilerplate.

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 one-parameter tool with no output schema, the description covers the scan scope, the verdict, and the cost. It is slightly incomplete because it does not elaborate on what the overall verdict looks like (e.g., a boolean, score, or risk label), but the provided information is sufficient for an agent to decide when to invoke it and what to expect at a high level.

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 single parameter is already fully documented in the schema as 'Pair id, symbol, or address,' so schema coverage is 100%. The description adds little beyond restating that the scan is 'for a pair'; it provides no additional formatting, constraints, or alternative input examples.

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 is specific: it enumerates concrete risk checks (honeypot, mint authority, LP lock, deployer history, verified source, top-10 concentration) for a pair and states it produces an overall verdict. This clearly distinguishes seranox_risk_scan from siblings like seranox_get_pair or seranox_list_pairs, which are not risk-assessment tools.

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 use case is implied: run this tool when you need a risk assessment of a pair. However, there is no explicit statement about when to prefer this over alternatives, no exclusions, and no guidance on the cost implication beyond noting the fee.

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 it returns health and API key status but doesn't specify response format or whether it makes network calls. It adds context beyond the name but not deeply.

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 efficiently conveys the tool's purpose. No filler or redundant information, front-loaded with the core concept.

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 zero-parameter status check without an output schema, the description is reasonably complete. It tells the agent what to expect (health and key status) and the relevance to routing. Minor gap: it doesn't describe return format, but that's not critical for this simple tool.

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 description doesn't need to explain parameters. The schema is already clear (no properties). The description adds value by explaining what the tool reports, which is sufficient.

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 it reports on the health of the Seranox API and whether the server has an API key, which is a specific and distinct purpose. It distinguishes this tool from siblings that perform actions like listing pairs or building routes, though it doesn't explicitly name an alternative.

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 checking API health and key presence before routing, but it doesn't explicitly state when to use it versus alternatives. It provides useful context for routing decisions but lacks clear 'when 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 add behavioral value by disclosing a cost side effect ('Burns 2 SERA') and the data returned. It does not mention read-only/write status, first errors, or whether the wallet must exist in a tracked list, leaving 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?

Two short sentences with zero fluff. The purpose, target, data fields, and cost are all packed efficiently and the most important information is front-loaded.

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 single-parameter tool with no output schema, the description covers what the user gets (list of five field categories) and the runtime cost. It could briefly state whether the wallet must already be tracked or what happens for unknown wallets, but the description is functionally adequate.

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 for the 'wallet' parameter is 100%, and the description only restates 'by address or label' without adding new semantics or prerequisites. The description therefore adds minimal value beyond the schema, earning the baseline 3.

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 provides wallet-level intel for one tracked wallet and enumerates the data fields returned (pattern tags, 30d PnL, win rate, activity, followers, bond). It does not name or differentiate against siblings like risk_scan, but the intended scope is evident.

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 one tracked wallet by address or label' implies when to use this tool (single-wallet intel), but there is no explicit guidance on when to prefer it over alternatives, nor any exclusions or prerequisites (e.g., whether the wallet must already be tracked).

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