solanaoracle

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

With no annotations provided, the description must disclose behavioral traits, but it only says 'monitoring,' which implies a read-only operation without explicitly stating it. It does not describe what data is returned, any limitations, or whether the tool is safe/non-mutating, leaving a significant gap.

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

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

The description is a single, concise phrase with no repetition or fluff. It is easy to scan, though it could benefit from being a full sentence or adding a bit more structure to convey the action explicitly.

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 that there is no output schema and no annotations, the description carries the burden of explaining what the tool returns, but it only mentions 'monitoring' without specifying metrics (e.g., volume, direction) or the scope of bridge flows. The tool is not self-explanatory enough for an agent to fully understand its capabilities.

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, and the instructions set a baseline of 4 for no-parameter tools. The description adds no parameter-specific details, but none are required because the schema is empty, so the baseline 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's focus ('Bridge deposit/withdrawal flow monitoring for Solana'), distinguishing it from siblings like sol_dex_volume or sol_defi_yields. However, it lacks a strong verb like 'get' or 'list,' making it more of a noun phrase than an explicit action, so it falls short of a perfect score.

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. The description does not mention any exclusions, prerequisites, or comparison to other Solana tools, leaving the agent to infer usage from the context.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool filters by TVL and category and covers all protocols, but does not describe output format, sorting, or any side effects. Since the tool is a read-only query by nature, these omissions are not severe, but the description lacks detail about what a 'comparison' actually returns.

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

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

The description is two concise sentences that front-load the core action ('Compare DeFi yields across all Solana protocols') and then summarize the filtering options. There is no redundant or filler content, making it efficient and easy to parse.

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

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

Given the tool has only two optional parameters, no output schema, and no annotations, the description provides basic functionality but lacks detail on the return structure or how results are presented. An agent might need to know the response fields (e.g., protocol name, APY, TVL) to invoke the tool correctly, but the description stays at a high level. It is adequate for a simple query tool but not fully 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?

The input schema already provides full descriptions for both parameters ('Filter keyword' and 'Minimum pool TVL' with a default), giving 100% coverage. The description merely restates that you can filter by TVL and category, adding no additional meaning or constraints beyond what the schema already documents.

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 compares DeFi yields across all Solana protocols, using the specific verb 'compare' and identifying the resource (DeFi yields). This distinguishes it from sibling tools like sol_dex_volume or sol_network_stats, which focus on different metrics.

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 first sentence provides clear context for when to use this tool: to compare yields across Solana protocols. It implies the use case effectively and, since no sibling tool appears to offer yield comparison, there are no exclusions or alternatives to mention. The description could be more explicit about not using it for other metrics, but the context is unambiguous.

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. It discloses the scope (72 exchanges) and scale ($1.6B+ daily volume), which gives useful context. However, it does not mention data freshness, historical depth, or whether the figure is trailing 24h, leaving gaps in understanding the behavior.

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, front-loaded with the core purpose, and includes a high-level statistic for orientation. It wastes no words and earns every element.

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 tool with no output schema, the description provides sufficient context: it names the metric (DEX volume/liquidity), the domain (Solana exchanges), and the scale (72 exchanges, $1.6B+ daily). It lacks detail on return format or time period, but for this complexity, it is nearly 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?

The tool has zero parameters, and the schema is an empty object with 100% coverage. The description adds meaning by clarifying what the tool returns (volume and liquidity) and its aggregation level, which is more than the schema alone. Since there are no params to document, the description fully covers the semantics.

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 DEX volume and liquidity data across a specific set of 72 Solana exchanges, making its purpose distinct from sibling tools like sol_defi_yields or sol_network_stats. The verb 'volume and liquidity' and scope '72 Solana exchanges' leave no ambiguity about what is returned.

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 queries about DEX volume and liquidity but gives no explicit guidance on when to choose this over alternatives. There are no exclusions, but also no mention of alternatives or contextual cues like 'use this when you need aggregated DEX metrics.' This is slightly better than no guidance, but not 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 must carry the full burden. It does disclose what data is returned (TPS, slot, etc.), which gives some insight into behavior, but it does not mention read-only nature, data freshness, rate limits, or any potential side effects. This is minimal but not misleading.

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 phrase that front-loads the core purpose ('Solana network health') and lists the key metrics. It is efficient, though it is a fragment rather than a complete sentence and could benefit from a verb for grammatical clarity.

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 tool with no output schema, the description covers the main data points, making it minimally viable. However, it fails to differentiate from sibling tools like sol_overview or sol_protocol_health, and does not clarify return format or granularity. Completeness is adequate but has clear gaps.

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

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

The input schema has zero parameters, so the baseline for parameter semantics is 4. The description adds no parameter info because none exist to document. It correctly implies the tool requires no inputs.

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

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

The description clearly identifies the tool as providing Solana network health metrics, enumerating specific data points (TPS, slot, epoch progress, block height, supply breakdown). This distinguishes it from sibling tools like sol_overview or sol_protocol_health by listing concrete outputs, though it lacks an explicit verb like 'get' or 'retrieve'.

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 offers no guidance on when to use this tool compared to siblings. There is no mention of alternatives, exclusions, or context such as 'use for network-level metrics' vs. 'use sol_dex_volume for DEX-specific stats'. It simply lists what it provides.

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 exist, and the description only lists output topics without disclosing behavioral traits such as data freshness, whether it is a read-only call, or any potential delays. The specific TVL value ($6.6B) may imply static data but this is not stated, leaving operational behavior unclear.

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, compact sentence with a clear structure (summary followed by a list). However, the hardcoded TVL ($6.6B) could become outdated and lead to misuse; this is a minor concern for conciseness but not overlong.

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 tool with no output schema, the description covers the key information an agent needs to understand the tool's purpose and contents. It could mention that it provides current ecosystem health data, but given the simplicity, it is nearly 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?

The tool has zero parameters, so the schema fully covers parameter semantics. A baseline of 4 is appropriate because no parameter explanation is needed, and the description clearly states what data will be returned.

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 a comprehensive Solana ecosystem overview, enumerating the specific metrics included (price, TVL, supply, TPS, epoch, protocol count). This distinguishes it from sibling tools that focus on narrower topics like DEX volume or validator info.

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 the sibling tools. The word 'comprehensive' implies a high-level starting point, but there is no explicit 'use this for...' or 'alternatives include...' to help an agent choose correctly.

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

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only lists the data fields (TVL, audit status, risk grade) but does not state that this is a read-only operation, or disclose any side effects, rate limits, or authentication needs. This is a significant gap for a tool that must be safely invoked.

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

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

The description is a single, well-structured sentence that front-loads the core purpose ('DeFi protocol health') followed by specific data points and supported protocols. Every word earns its place, with no redundant 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 simple tool with one required parameter and no output schema, the description is largely complete. It specifies the return fields (TVL, audit status, risk grade) and enumerates supported protocols. It does not describe the exact output format or error handling, 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 fully describes the single 'protocol' parameter with examples. The description adds 'Kamino' and 'etc.' to the list, which is marginal additional value. Since schema coverage is 100%, 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 identifies the tool's purpose as reporting DeFi protocol health metrics (TVL, audit status, risk grade) and lists supported protocols, which distinguishes it from sibling tools focused on yields, volume, or network stats. However, it lacks an explicit verb like 'get' or 'return', making it slightly less direct.

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. It does not mention that for yields one should use sol_defi_yields or for volume sol_dex_volume, nor does it state any exclusion criteria. The context of siblings is present only in external context, not in the description.

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. It only mentions the output (protocols ranked by TVL) but does not disclose whether this is a read-only operation, whether the list is exhaustive, how rankings are ordered, or what data fields are returned. Minimal behavioral context is provided.

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 unnecessary words. It efficiently conveys the core function 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?

For a simple 0-parameter tool with no output schema, the description is largely sufficient to understand what the tool returns. It lacks minor details (e.g., whether TVL is in USD, ordering direction) but is complete enough for a basic reference list. The sibling context further clarifies its niche.

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 adds no parameter-specific semantics. The baseline for 0 parameters is 4, and the description does not contradict or confuse parameter usage. No additional param information is needed.

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 all Solana DeFi protocols ranked by TVL, using a specific verb ('list' implied) and resource ('Solana DeFi protocols') with a clear scope ('ranked by TVL'). This distinguishes it from sibling tools like sol_defi_yields (yields) and sol_dex_volume (trading volume).

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 explicit guidance is provided on when to use this tool versus alternatives. It does not mention any sibling tools or situations where this tool is preferable, leaving the agent to infer from the description alone.

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

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It merely states the topic ('supply and risk') without explaining what the tool does (e.g., returns a report, list, or metrics), whether it's read-only, or any side effects. This lack of detail leaves the agent uncertain about expected behavior.

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 sentence that efficiently conveys the tool's scope. It is front-loaded with the key topic and includes example tokens, all in a compact format.

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 no output schema and no annotations, the description is incomplete for an agent to understand what data will be returned. 'Supply and risk' is vague; it doesn't specify the structure of results, whether it's a list or aggregate, or what metrics define 'risk.' The complexity is low (no params), but the missing output details leave a significant gap.

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

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

The tool has zero parameters and the schema is empty, so schema coverage is 100%. Per the baseline for 0 parameters, the description need not add parameter details; there are none to document.

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's focus: stablecoin supply and risk on Solana, mentioning specific tokens. This distinguishes it from sibling tools like sol_token_risk (general token risk) and sol_protocol_health (protocol-level health).

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 stablecoin-specific analysis but provides no explicit guidance on when to choose this over alternatives. It doesn't mention exclusions or contrast with sibling tools, leaving usage to inference.

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 burden of behavioral disclosure. It does disclose the nature of checks (read-only analysis of authority, listing, supply), but doesn't explicitly state that it's read-only, describe the returned risk scale, or mention any side effects or limitations.

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 sentences, front-loads the core purpose, and every word earns its place. It is concise without sacrificing important 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?

The tool is simple with one parameter, but because there is no output schema, the description should explain what the returned risk score represents (scale, higher/lower meaning). This is missing, leaving interpretation ambiguous, though the 'ideal for Pump.fun screening' hint provides some context.

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 already describes the only parameter ('SPL token mint address') with 100% coverage. The description adds no additional parameter detail beyond what the schema 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 identifies the tool as a risk scorer for Solana SPL tokens and lists specific checks (mint/freeze authority, CoinGecko listing, supply), making it easy to distinguish from sibling tools like sol_stablecoin_risk or sol_wallet_analysis.

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?

States the intended use case ('Ideal for Pump.fun token screening'), giving concrete context for when to use it. It doesn't explicitly exclude alternatives or mention sibling tools, but the guidance is clear and actionable.

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?

There are no annotations, so the description alone must disclose behavioral traits. It states what the tool returns, but does not explicitly confirm it is read-only, mention data freshness, or describe any side effects. It does not contradict annotations, but it leaves important safety and behavior information unstated.

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 phrase that packs significant meaning into few words. It avoids unnecessary filler and efficiently conveys the tool's purpose and key outputs.

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 description lists the primary outputs but leaves 'concentration analysis' undefined and does not clarify the response structure or measurement methodology. Since there is no output schema, the description should be more explicit about what the returned data looks like to be fully 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?

The tool takes zero parameters, and schema coverage is 100% (no params to document). The description does not need to compensate for schema gaps, so the baseline of 4 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 a validator overview and enumerates specific outputs (active/delinquent counts, top 10 by stake, concentration analysis). This distinguishes it from sibling tools like sol_network_stats, which likely focus on network-wide metrics rather than validator-specific data.

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 instead of alternatives such as sol_overview or sol_network_stats, nor does it mention any exclusions. The usage context is implied but not 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 provided, so description carries full burden. It implies read-only analysis and lists expected outputs, but doesn't disclose details like response format, error handling, or data freshness. This is adequate but not deeply 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?

One concise sentence, front-loaded with 'Analyze a Solana wallet' and immediately lists key outputs. No wasted words.

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 without output schema, the description lists the three main result categories, giving sufficient context. However, it lacks explicit statement of return structure or limitations, so not fully 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 covers the single 'address' parameter with 'Solana wallet public key' (100% coverage). Description adds context that the analysis includes balance and holdings, but parameter semantics are already fully documented.

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?

Clearly states the tool analyzes a Solana wallet and lists specific data points (SOL balance, USD value, SPL token holdings), distinguishing it from sibling tools that focus on network stats, DEX volume, 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?

Description implies usage when you need wallet balance/holdings, but doesn't explicitly mention when to use it instead of other sibling tools or any exclusions. Sibling names provide some contrast but the description itself lacks explicit 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?

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states 'Monitor recent transactions' without explaining what 'monitor' entails (e.g., polling, streaming, one-time fetch), what 'recent' means, or what the output format is. Mutability, permissions, and rate limits are also not addressed.

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

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

The description is a single sentence with no filler. It is appropriately sized and front-loaded with the action and resource.

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 should explain what 'monitoring' returns or how it behaves over time. It lacks important context about expected results and use cases, especially given the existence of similarly named sibling 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?

The input schema has one parameter 'address' described as 'Solana address to monitor', providing 100% coverage. The description adds no further semantic detail beyond this, 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 'Monitor recent transactions for any Solana address' has a specific verb (monitor) and resource (recent transactions for a Solana address). It is clear and unambiguous, but it does not distinguish this tool from siblings like sol_wallet_analysis, which likely also involves monitoring or analyzing wallet activity.

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. Sibling tools such as sol_wallet_analysis or sol_bridge_flows might serve overlapping purposes, but the description offers no context or exclusions.

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