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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds 'No payment required' and specifies what is checked (health, version, status), providing useful context beyond the 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 concise with two short sentences. The first states the core purpose, and the second adds usage guidance. No unnecessary words or repetition.

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 health check tool with one optional parameter, strong annotations, and no output schema, the description sufficiently covers purpose, usage, and constraints. Nothing essential is 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?

The input schema has 100% coverage, including a description of the 'verbose' parameter. The tool description adds no additional parameter guidance, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool checks CryptoGuard API health, version, and service status, with a specific verb and resource. It is easily distinguished from sibling tools that handle trade validation, token scanning, and searches.

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 explicitly says to use this to verify the service is running, providing clear usage context. It does not mention alternatives, but the health check is unique among siblings, so this is sufficient.

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 declare readOnlyHint, idempotentHint, and destructiveHint=false, establishing safety. The description adds behavioral detail by specifying the six risk factors and the 0-100 scoring scale, which informs the agent what the tool will compute. No contradictions with 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?

Two concise sentences: the first states the purpose and output details, the second gives a practical example. No wasted words, 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?

With strong annotations, complete schema, and a description that names the six risk factors and scoring range, the tool is adequately specified for selection and invocation. The lack of an output schema is partially compensated by the description's reference to 0-100 scores, though exact return structure is not specified.

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%, with both 'chain' and 'pair_address' already described. The description's example ('new Solana pair') reinforces the parameters but does not add substantive new meaning beyond the schema, 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 clearly states the tool's purpose: 'Assess rug pull risk for a specific DEX trading pair.' It identifies the resource (DEX pair) and the specific action (rug risk assessment), and the list of six risk factors differentiates it from siblings like validate_trade or scan_token.

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 clear context: it is used to evaluate a DEX pair's rug pull risk, with an explicit example ('check if a new Solana pair is a potential rug pull'). It does not name alternatives or state when not to use it, but the use case is sufficiently clear from the tool's focus.

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?

Beyond the readOnlyHint and destructiveHint annotations, the description adds meaningful behavioral context: it performs peer-tier comparison and returns anomaly scores, risk level, and explanations. This goes beyond the safety profile already declared by annotations, giving the agent a clearer picture of the tool's operation and output.

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 highly concise, consisting of two sentences plus an example. Every sentence contributes meaningful information: the core functionality, the tier-matching behavior, and the output summary. No fluff or 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?

Given there is no output schema, the description compensates by listing the return types (anomaly scores, risk level, explanations). It adequately explains the input and the comparison logic, making the tool understandable for a read-only scan operation. It lacks details on rate limits or edge cases, but for this complexity level, it is sufficient.

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 covers both parameters with clear descriptions (coin_id and sensitivity). The description enhances this by providing a concrete example ('scan solana') that demonstrates parameter usage in context, adding value beyond the schema definitions.

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 scans a single token for anomalous market behavior using a specific method (WaveGuard physics-based anomaly detection). It also distinguishes itself from sibling tools by specifying tier-matched peer comparison, making it unique among the listed 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 example 'scan solana' provides a concrete use case, making it clear when to use the tool. It implies the tool is for checking anomaly metrics on a single token, but it does not explicitly contrast with alternatives like rug_check or validate_trade, so it lacks explicit 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?

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds useful behavioral context about returning CoinGecko coin IDs and demonstrates usage with an example, going beyond the 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 extremely concise, with purpose, usage guidance, and an example in just two sentences. No redundant information; every sentence serves a clear function.

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 search tool with a single parameter and no output schema, the description is fully adequate. It covers purpose, usage context, and example, while annotations cover safety. It's complete for an agent to select and invoke 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 100%, so the parameter is already well-documented. The description adds marginal value by clarifying the search purpose and providing an example, but doesn't uniquely enrich the parameter semantics 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 clearly states the tool's function: searching for a token's CoinGecko coin ID by name, symbol, or contract address. It also distinguishes itself from sibling tools by explicitly referencing scan_token and validate_trade as tools that require this coin_id.

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?

Provides explicit when-to-use guidance: 'Use this first if you're unsure of the correct coin_id for scan_token or validate_trade.' This names alternatives and gives clear usage context, plus an example for added clarity.

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 establish read-only, idempotent, non-destructive behavior, and the description adds a concrete behavioral model: five named checks and a tri-state verdict. It also implies no state mutation by focusing on pre-execution validation. No contradiction with annotations found.

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 plus a one-line example, with the core purpose stated first. It lists the five checks efficiently and the example illustrates usage without redundancy. Every word contributes informational 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 tool with five parameters and no output schema, the description gives enough context to select and invoke it correctly: it explains the verdict output, the checks performed, and the accepted token formats from the schema. It could be slightly stronger by noting that certain parameters like pair_address are conditionally used for one of the five checks, but the overall picture is sufficient.

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 provides 100% parameter descriptions, so the baseline is 3. The description adds a concrete example ('buying $500 of PEPE') that maps token and amount_usd, but it doesn't explain parameter-specific formats or dependencies (e.g., that pair_address is needed for the rug pull check) 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 specific verb ('Validate') and resource ('a crypto trade'), immediately distinguishing this as a pre-execution validation tool. It enumerates the five checks and names the output verdict (PROCEED/CAUTION/BLOCK), clearly differentiating it from the rug_check sibling and signaling that this is the comprehensive trade validation 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?

The instruction to 'validate BEFORE execution' gives clear usage context, and the example ('before executing') reinforces the intended timing. However, it doesn't explicitly exclude alternatives like rug_check for specialized checks or mention validate_trade_plus for potentially deeper validation, so it stops short of a full when/when-not guide.

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