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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only says 'decode', which implies a pure transformation, but it does not disclose that this is a read-only operation, that it may revert on invalid data, or that it returns a list of decoded values matching the provided types. This lack of detail prevents the agent from anticipating errors or side effects.

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, succinct sentence that starts with the verb 'decode' and clearly states the input and output. It is appropriately brief for a simple tool, though it could include a bit more context without becoming verbose.

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?

This is a low-complexity tool with two required parameters and no output schema. The description and schema together provide enough to understand its basic function, but the lack of usage guidance and details about return values or error handling leaves the description incomplete for an agent that needs to select it correctly among many related utilities.

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 covers both parameters (types and data) with descriptions, and schema coverage is 100%, so the baseline is 3. The description adds no additional meaning, but the schema already provides sufficient detail for the agent to understand the 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?

The description 'ABI decode encoded data back to values' clearly states the tool's function: decoding ABI-encoded data into human-readable values. The verb 'decode' and resource 'encoded data' are specific. It distinguishes from sibling tools like abi_encode, which performs the inverse operation, though it does not explicitly name alternatives.

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 such as decode_transaction_data or encode_call_data. The description does not mention typical use cases, prerequisites, or when not to use it. This leaves the agent without context to decide between similar tools.

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

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

With no annotations provided, the description must carry the full burden of behavioral disclosure, but it only restates the encoding functionality. It does not specify the output format (e.g., hex string), error behavior, supported Solidity types, or side effects. 'Standard Solidity encoding' adds a small hint but is not 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 extremely concise and well-structured, with no wasted words. While it is short and could be seen as under-specified, the length is appropriate for a simple utility tool. It front-loads the key 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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what the encoded output looks like, whether it supports dynamic types, or any special considerations. The schema covers parameters, but the return value and edge cases remain undocumented.

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 fully documents both parameters with 100% coverage: 'types' is described as 'Array of Solidity types' and 'values' as 'Array of values corresponding to the types'. The description itself adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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

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

The description clearly states the action (ABI encode) and the resource (parameters), with 'standard Solidity encoding' indicating which encoding scheme is used. It doesn't explicitly contrast with sibling tools like encode_call_data or encode_packed, but the name and description are sufficiently clear.

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 such as encode_call_data, encode_packed, or abi_decode. The description implies usage for encoding parameters but provides no contextual rules or alternative references.

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 the burden of disclosing that this is a mutating on-chain transaction requiring a private key and incurring gas costs. The description simply states the intent without explaining that user funds are at risk, that a transaction is signed and broadcast, or that slippage can affect the outcome. The schema includes a security note about privateKey, but the description itself adds no behavioral 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 description is a single, concise sentence without redundant words or filler. It is front-loaded with the action, making it easy to parse. However, given the tool's complexity (8 parameters, a DeFi transaction), the brevity borders on under-specification, though not enough to lower the score to 3.

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 performs an on-chain transaction, but the description omits essential context: what the result is (e.g., transaction hash), what the user should prepare (approvals, balance checks), and network-specific defaults. With no output schema and no annotations, this description leaves the agent without enough information to invoke the tool safely.

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 does not elaborate on parameter interactions, typical values, or edge cases; it is entirely dependent on the input schema. Thus, it does not add meaning beyond what the schema already provides.

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

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

The description clearly states the verb 'Add' and resource 'liquidity to a DEX trading pair', making the primary function immediately apparent. However, it does not differentiate from sibling tools like add_liquidity_native, which also adds liquidity but with native tokens, so the scope is not fully unambiguous.

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 no guidance on when to use this tool versus alternatives such as add_liquidity_native or remove_liquidity, nor does it mention prerequisites like token approvals, balance checks, or network considerations. It is a single declarative sentence with no procedural or comparative 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?

No annotations are provided, so the description must disclose behavioral traits. It only states the high-level function without mentioning that this executes an on-chain transaction, requires a private key, applies slippage, or interacts with a DEX. This lacks transparency for a mutating tool.

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, clear sentence with no unnecessary words. It front-loads the core action and directly states the key pairing 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?

Given the tool's moderate complexity (7 parameters, 4 required) and no output schema, the description is adequate but incomplete. It doesn't mention that this submits a transaction, consumes gas, or produces a tx hash, but the schema's detailed parameter descriptions partially compensate for this 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 description coverage is 100%, so the parameters are already well-documented. The description adds minimal extra value by clarifying 'native token' and giving examples, but it doesn't significantly enhance parameter understanding 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 action ('Add liquidity') and the specific resource ('with native token (ETH, BNB, MATIC) and another token'). It distinguishes itself from sibling tool 'add_liquidity' by explicitly mentioning native tokens, making the scope obvious.

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 phrase 'with native token' – an agent can infer to use this tool when adding liquidity with ETH/BNB/MATIC rather than a token-token pool. However, there is no explicit guidance on when to choose this over 'add_liquidity' or any exclusions, leaving room for ambiguity.

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. It only says 'check', implying a read-only operation, but does not disclose whether there are any side effects, required permissions, or what the output contains. This lack of behavioral detail 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 only four words, which is extremely concise. It captures the essence without wasting words, though it may be under-specified. Still, for the level of detail provided, it is 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?

The tool is simple with one optional parameter and no output schema. The description gives the basic idea but does not explain what 'triggered alerts' means or what the response format is. This is adequate for a straightforward check but leaves some 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?

The schema provides a clear description for the single parameter alertIds ('Specific alert IDs to check (all if omitted)'). The description adds no additional meaning beyond the schema, and since schema coverage is 100%, a 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 'Check for triggered alerts' clearly states the action (check) and the resource (triggered alerts). It is easy to understand what the tool does, but it does not differentiate itself from the sibling tool 'alert_list', which could also be interpreted as checking alerts.

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 like alert_list, alert_history, or other alert-related tools. The description does not provide context for choosing this tool over similar ones.

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 the full burden of behavioral disclosure. It simply states the action without indicating that clearing all alerts is likely destructive, irreversible, or affects all configured alerts. The agent has no information about side effects or whether confirmation is required.

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, concise sentence with no wasted words. While it is under-specified for a destructive operation, the conciseness itself is appropriate given the zero-parameter schema, though it could be slightly more informative.

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 destructive 'clear all' operation with no annotations and no output schema, the description is severely incomplete. It does not explain what 'alerts' refers to, whether the action is permanent, or what the outcome is. This is a significant gap that could lead an agent to invoke it without adequate 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?

The input schema has zero parameters, so the baseline is 4. The description correctly says nothing about parameters, and there is no need to compensate for missing schema documentation.

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 'Clear all alerts' uses a specific verb (clear), resource (alerts), and scope (all), making the purpose immediately clear. It implicitly distinguishes from sibling alert tools by specifying the 'all' scope, though it does not explicitly name alternatives.

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 no guidance on when to use this tool versus alert_delete, alert_pause, or others. There is no mention of prerequisites, scenarios, or cautionary notes, leaving the agent without direction for appropriate usage.

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 only states 'create an alert' but does not disclose side effects, persistence, notification mechanism, or how to manage created alerts. The agent is left unaware of outcome or lifecycle, which is insufficient for a creation operation.

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 zero redundant words, front-loading the core action and object. It is appropriately sized for the simple operation it describes, making it efficient and scannable.

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 moderate complexity (nested filter, 4 parameters) and no annotations or output schema, requiring the description to explain more about what creating an alert entails. It lacks information on return values, how to verify success, or any prerequisites. The description is too minimal to be fully actionable for an agent.

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 all four parameters (chain, filter, eventSignature, contractAddress) have descriptions in the schema. The tool description adds no additional semantics beyond those already present, resulting in baseline score as per coverage guidelines.

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 ('create') and resource ('alert for specific smart contract events'), clearly distinguishing it from sibling alert tools like alert_price or alert_gas. Even without naming alternatives, the scope is unambiguous and matches the tool name.

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 smart contract event monitoring, but does not explicitly state when to use this vs alternatives (e.g., alert_price, alert_wallet_activity). No exclusions or context are provided; it relies on the tool name and sibling context to infer appropriate use.

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 of disclosing behavior. It only states the action without indicating whether deletion is permanent, requires confirmation, affects history, or has any side effects. This is a significant gap for a mutation tool.

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 short and front-loaded, but it is under-specified to the point of being nearly tautological. It is not unnecessarily verbose, yet it sacrifices informational value for 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 simple deletion tool with one parameter and no output schema, the description lacks essential context like reversibility, permission requirements, or any behavior beyond the literal action. The sibling tools and schema reveal there is more nuance (e.g., alert_clear_all) that isn't addressed.

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 covers 100% of parameters with a clear 'Alert ID to delete' description. The tool description adds nothing beyond the schema, but the schema itself is sufficient for a single-parameter 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 'Delete an alert' clearly states the verb and resource with the specific action. It is unambiguous for the core purpose, though it doesn't differentiate from sibling alert_clear_all, which is a bulk deletion action.

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 provided on when to use this tool versus alternatives like alert_clear_all or alert_pause. There are no contextual hints, preconditions, or exclusions mentioned.

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 present, so the description must disclose behavioral implications. It only says 'Create an alert' without explaining that this is a persistent side-effecting operation, how to manage the alert afterward, or any prerequisites or limits. The lack of behavioral information is a significant gap for a creation tool.

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 earns its place by clearly naming the action and subject.

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 no output schema and no annotations, and the description does not cover expected return values or subsequent management options (alert_list, alert_pause, etc.). For a side-effecting creation tool in a rich alert ecosystem, this level of information is insufficient.

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 and schema explain that chain, condition, and targetGwei are used for gas price conditions, but neither adds deeper meaning such as how condition and targetGwei interact (e.g., alert when gas price below target). The description contributes minimal value beyond the structured 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?

The description clearly states the tool's function - creating an alert for gas price conditions - using a specific verb and resource. It differentiates from sibling alert tools by specifying 'gas price', unlike alert_price, alert_whale_movement, etc., though it omits details on how conditions are defined.

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 provided on when to use this tool versus other alert creation tools or how it fits into the alert management lifecycle. The description offers no context for selecting this tool over alternatives like alert_price or alert_contract_event.

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 available, the description carries the full burden of behavioral disclosure. It only states the basic purpose, omitting any details about return format, pagination, ordering, or the nature of the history. This is minimal for a tool that retrieves data.

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 efficient sentence with no unnecessary words. It is front-loaded and to the point, earning its place without 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?

The tool is simple with only two optional parameters, but the description lacks any mention of output structure or usage context. It is minimally viable but has clear gaps, such as missing differentiation from alert_list and no indication of result format.

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 describes both parameters (limit and alertId) with clear descriptions, achieving 100% coverage. The description adds no additional parameter semantics, so the baseline score of 3 applies.

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

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

The description clearly states it retrieves 'history of triggered alerts', using a specific verb and resource. It distinguishes itself from sibling alert tools by indicating historical data retrieval, though it doesn't explicitly contrast with alert_list.

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 provided on when to use this tool versus alternatives like alert_list or alert_check. The description gives no context for choosing this over other alert-related tools.

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

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

No annotations are provided, so the description must disclose behavioral traits. It indicates a mutation (create) but does not explain whether the alert is persistent, how it is managed, what response to expect, or any prerequisites. This is insufficient for a creation tool.

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 filler. It communicates the core purpose immediately.

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 schema covers parameters and the purpose is clear, the tool lacks annotations and an output schema. The description does not explain the alert lifecycle or how the created alert will be managed, making the complete picture incomplete. However, given the simplicity of the tool, it is not severely inadequate.

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?

All four parameters have descriptions in the schema (100% coverage), including enums for condition and chain and units for threshold. The tool description itself adds no additional parameter details, so the baseline of 3 applies.

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

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

The description uses the specific verb 'Create' and clearly identifies the resource: an alert for liquidity changes in a pool. This distinguishes it from sibling alert tools like alert_price, alert_gas, etc.

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 a user wants to monitor liquidity changes, but it provides no explicit guidance on when to prefer this tool over other alert creation tools. No alternatives or exclusions are mentioned.

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, but it only states 'List all alerts' without revealing any behavioral traits such as pagination, ordering, scope (e.g., user-specific vs. global), or whether it returns only current alerts versus historical ones. This is minimal and leaves significant 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?

The description is a single succinct sentence, 'List all alerts', that immediately states the tool's purpose. There is no wasted text, 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?

This is a simple list tool with one optional filter, and the schema covers the filter. However, with no output schema and no mention of what fields or format the alert list returns, the description is only minimally adequate for an agent to fully understand the tool's output and edge cases.

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 fully documents the single 'status' parameter with enum values and a default, yielding 100% schema description coverage. The description adds no parameter-level detail, so it does not improve upon what the schema already provides, warranting the baseline score of 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 'List all alerts' clearly identifies the action (list) and resource (alerts). It is specific enough to convey the tool's core function, though it does not explicitly distinguish itself from the similarly named sibling tool 'alert_history', so it misses the full sibling-differentiation criterion.

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 no guidance on when to use this tool versus alternatives like 'alert_history' or 'alert_check'. There is no mention of prerequisites, typical use cases, or exclusions, so it offers no practical usage direction beyond the obvious.

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 of behavioral disclosure, but it merely restates the tool's name ('Pause an active alert'). It does not explain side effects, reversibility, what happens if the alert is already paused, or whether pausing is idempotent. This adds no value beyond the tool name.

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 one short phrase with no wasted words and is front-loaded. It is appropriately brief for a simple single-parameter tool, though it is quite terse and could have included more helpful context without becoming verbose.

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 a simple schema and no output schema, but with no annotations the description should clarify what pausing entails (e.g., temporary suspension of notifications, effect on ongoing alerts, response behavior). The current description is too sparse to be considered complete for an agent to use correctly without additional assumptions.

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 fully covers the single parameter with a description ('Alert ID to pause'), giving 100% schema coverage. The description itself adds no additional semantic detail about the parameter format, constraints, or behavior, 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 uses a specific verb ('Pause') and a clear resource ('an active alert'), which clearly states what the tool does. It is distinguishable from sibling alert actions like alert_resume or alert_delete, though it does not explicitly 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?

There is no guidance on when to use this tool versus alternatives. It does not say when pausing is appropriate, what prerequisites exist, or how it differs from deleting or resuming an alert. The qualifier 'active' implies a condition but offers no actionable 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, the description must disclose behavioral traits, but it only says 'create', implying a state change. It does not explain what happens after the alert triggers, whether it repeats, how to manage it, or any required authentication. This is a significant gap for a mutation tool.

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 efficient sentence with no filler words. It is appropriately front-loaded, though it could include a bit more context about alert conditions without becoming verbose. It earns a strong score for structure but not a 5 because it omits potentially useful details.

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 state-changing tool with no output schema, the description is minimally complete. It does not explain what the response looks like, whether an alert ID is returned, how the alert is delivered, or how to manage it later. The schema handles parameters but not the tool's effects or lifecycle, leaving the agent without enough context for full usage.

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 provides 100% coverage with clear descriptions for all parameters (symbol, condition, targetPrice, repeat), including an enum. The description adds no extra meaning beyond the schema, but because the schema is complete, 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 uses a clear verb+resource structure ('Create a price alert for a cryptocurrency'), and 'price alert' distinguishes it from sibling alert tools like alert_whale_movement or alert_gas. It could be more detailed about the alert conditions, but the core purpose is unambiguous.

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 provided about when to use this tool versus alternatives. It does not mention prerequisites, when a price alert is preferable to other alert types, or that it can be managed via alert_list/alert_delete. The description offers no 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action and gives no information about side effects, idempotency, error conditions, or required permissions.

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 concise sentence with no superfluous wording. However, it is so brief that it under-specifies the tool's context, so it is not a perfect 5.

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

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

For a simple one-parameter tool, the minimal description might be an adequate baseline, but it omits behavioral expectations such as whether the alert must be paused, what the response looks like, and error handling. Since there is no output schema to clarify, the description could be more 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 coverage is 100% and the parameter has a description ('Alert ID to resume'), so the schema already documents the parameter. The description adds no additional semantic context beyond that.

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 action ('Resume') and the resource ('a paused alert'), which distinguishes it from related tools like alert_pause and alert_delete. It is specific and unambiguous.

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 on when to use this tool versus alternatives. It does not mention prerequisites, when the alert should be paused, or contrast with alert_pause and alert_list. The description is purely definitional.

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

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

No annotations are provided, so the description must carry the behavioral transparency burden. It only states that an alert is created; it does not disclose persistence, delivery mechanism, duplicate behavior, permissions, or return value. This is a significant gap for a mutation tool.

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 filler. Every word contributes to the core purpose.

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

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

With no annotations and no output schema, the description is too sparse. It doesn't explain what the alert does after creation, how the result is returned (e.g., alert ID), or how it fits into the alert management workflow (list/pause/delete).

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?

All 3 parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds no extra parameter semantics beyond the phrase 'any activity,' but the schema already documents chain, address, and activityTypes defaults.

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 ('Create') and identifies the resource ('an alert for any activity on a wallet'). It clearly distinguishes from sibling tools like get_wallet_activity (read) and alert_price (specific alert type).

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 provided on when to use this tool versus alternatives such as alert_whale_movement, alert_contract_event, or ws_subscribe_wallet. It also doesn't mention the alert management lifecycle (alert_list, alert_delete, etc.).

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

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states that it creates an alert, without mentioning side effects (e.g., persistence, notification mechanism), prerequisites, or what happens upon creation. This is insufficient for a creation/mutation tool.

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 redundancy. It conveys the essential purpose efficiently with a clear verb and resource, making it appropriately sized and well-structured.

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 moderate complexity, the description covers purpose and the schema covers parameters, but it lacks guidance on post-creation behavior (e.g., how alerts are delivered or managed) and doesn't reference sibling alert management tools like alert_list or alert_delete. With no output schema, the agent is left without information on the return format.

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 covers 100% of parameters with descriptions, setting a baseline of 3. The description adds no additional meaning beyond the schema — 'large transactions' is essentially synonymous with the minValueUSD parameter description. No extra semantic value is provided.

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 creates an alert for large transactions on a token or wallet, with a specific verb and resource. It distinguishes from other alert tools by focusing on 'large transactions' (whale movements), though it doesn't explicitly differentiate from siblings like alert_wallet_activity or wallet_whale_movements.

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 the primary use case (creating whale alerts) but provides no explicit guidance on when to choose this over alternatives such as alert_wallet_activity or alert_price. No exclusions or alternative recommendations are given, making usage context only implied.

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 disclosing behavioral traits. It only says 'Analyze' with no mention of whether this is a read-only operation, what output format to expect, whether any network calls are made, or any side effects. The description gives no behavioral context beyond the verb itself, which is insufficient for a tool with no annotation support.

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 concise sentence with no fluff or redundancy. It front-loads the action and the subject. While it could be slightly more descriptive, the structure is efficient and all the words contribute to the meaning, earning a 4 rather than a 5 because it lacks useful 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?

For a security analysis tool with no output schema and no annotations, the description is too terse. It does not explain what 'dangerous permissions' means, what kind of results the agent should expect (e.g., list of risky functions, ownership details), or any caveats about supported networks. This leaves the agent under-informed about the tool's actual capabilities and return value.

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%, with both 'network' and 'contractAddress' having clear descriptions. The description adds no extra meaning beyond the schema, as it only mentions 'contract' which aligns with the contractAddress parameter. Baseline 3 is appropriate because the schema already documents parameters adequately.

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 ('Analyze') and resource ('a contract') with a clear focus on 'dangerous permissions and admin functions'. This makes the core purpose understandable. However, it does not differentiate from neighboring security analysis tools like analyze_token_security or check_approval_risks, so it misses the sibling differentiation that would earn a 5.

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

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

There is no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or alternative tool names. The phrase 'dangerous permissions' implies a security analysis use case, but that is implied rather than explicit, leaving the agent without clear selection criteria.

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

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It adds useful context: the cost per request ($0.001) and that it is AI-driven analysis. However, it does not disclose whether articleId or articleUrl is required, how targetCoins affects the analysis, or what the response format looks like. Some transparency is provided, but 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?

The description is two short sentences that are front-loaded with the core purpose, immediately followed by cost and methodology. Every piece of text earns its place with no padding or repetition, making it highly efficient and scannable.

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 is low-complexity and the input schema is well-documented, but the absence of an output schema means the description should ideally clarify the return format or the required input combination. It does neither. However, the basic purpose and cost are clear, making it minimally viable for an agent to use effectively.

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 full descriptions for all three parameters (articleId, articleUrl, targetCoins), giving 100% schema coverage. The description adds no additional parameter-level meaning, so the baseline score of 3 applies. It neither compensates for gaps nor adds redundant details.

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: 'Analyze potential market impact of a news article' and specifies the domain ('how news might affect crypto prices'). This verb+resource+scope formulation distinguishes it from news-fetching or summarization sibling tools like 'get_defi_news' and 'summarize_article'.

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 the usage context: when you have a news article and want to assess its potential effect on crypto markets. It does not explicitly name alternatives or exclusions, but the purpose is distinct enough to guide selection. A clear context is present without explicit when-not 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?

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It only states the analysis intent and does not disclose methodology, read-only nature, network implications, rate limits, or output format.

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 states the purpose directly with no filler. It is efficient and front-loaded, though it could include more detail without becoming verbose.

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 complexity of security analysis and the large set of overlapping sibling tools, this one-sentence description is insufficient for an agent to select the tool correctly. It lacks information about what specific checks are performed, what output is returned, and how it differs from other security tools.

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

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

Schema coverage is 100% as both network and tokenAddress have descriptive text in the schema. The description adds no additional parameter semantics beyond what the schema already provides, so 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 uses a clear verb ('Analyze') and resource ('token contract') with a specific purpose ('security risks and red flags'). It is unambiguous but does not differentiate from numerous sibling security tools like detect_rug_pull_risk or goplus_token_security.

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 provided on when to use this tool versus alternatives such as analyze_contract_permissions or goplus_rugpull_detection. No exclusions, prerequisites, or context are mentioned.

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. It fails to mention that this is an on-chain transaction requiring a private key for signing, likely incurs gas costs, and modifies the NFT's approval state. The only behavioral hint is the parenthetical marketplace names.

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, directly front-loaded sentence with no unnecessary words. It immediately states the action and the target, making it 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?

This is a transaction tool with 6 parameters and no output schema, yet the description provides no information about execution flow, expected results, or prerequisites. The schema covers parameter formats, but the description does not explain what 'approve' entails operationally (e.g., gas, signing, state change).

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 a 100% description coverage for all 6 parameters, so the tool description does not need to repeat them. The description adds no extra parameter semantics beyond the schema, but the schema itself is sufficiently detailed, warranting the baseline score.

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 action (approve), the resource (an NFT), and the context (for sale on a marketplace, specifically Seaport/OpenSea). This distinguishes it from sibling tools like approve_token_spending (ERC20) and revoke_nft_approval.

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 no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., owning the NFT, being on the correct network) or situations where a different approval tool would be more appropriate.

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, but it only states the high-level action. It does not disclose that this modifies on-chain state, broadcasts a transaction, requires gas, or carries security risks such as exposing funds to the spender, which is critical for a mutation tool.

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 efficiently conveys the core action with no filler. It is concise and front-loaded, making it easy for an agent to parse quickly.

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

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

For a tool that approves token spending, the description is minimal and incomplete. It lacks mention of return values, transaction processing, security implications, or behavior on different networks, leaving important operational context to the schema. Given no output schema and no annotations, 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 description adds no parameter details beyond the input schema, but schema coverage is 100% with descriptive entries for each field. The baseline of 3 applies because the schema already documents all parameters, including the 'unlimited' option for amount and security note for privateKey.

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 specific verb 'Approve' and clearly identifies the resource ('a spender to use your ERC20 tokens'), which distinguishes it from sibling operations like revoke_token_approval and check_token_allowance. It precisely states what the tool does without ambiguity.

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 no guidance on when to use this tool versus alternatives such as checking existing allowances or revoking approvals. It also omits prerequisites, such as ensuring the token address is correct or that the spender address is trustworthy.

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 provides no behavioral details beyond the bare function. With no annotations to indicate read-only status, rate limits, or other traits, the burden falls on the description, which only states the basic action. It does not disclose whether this returns a fee estimate, a per-gas-unit price, or any network-specific nuances.

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 at five words, with no redundant or extraneous content. It gets straight to the point and is easy to read.

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