Stock Bloc

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

With no annotations, the description carries the full burden and partially meets it: it discloses the output shape (quotes, XBRL changes, riskDelta), the payload-size tradeoff via compact, and a hard cost of $0.05. It says nothing about permissions, latency, rate limits, or error behavior, and the phantom 'mode'/'compact' flags muddy the contract. Partial but useful disclosure.

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?

Front-loaded with the value statement, then use hints, then savings and cost, in four compact sentences with no filler. Slightly weakened by the stray references to non-existent flags, but overall well-sized for the tool's complexity.

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 3-parameter tool with no output schema, describing the return content is genuinely valuable and largely done here, and cost is disclosed. But the description references parameters that do not exist, which undermines confidence that it accurately describes this tool's interface. Adequate but with a real accuracy 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 real parameters (ticker, filingType, question) are already documented and the baseline would be 3. However the description references 'mode=diff' and 'compact=true', neither of which exists in the input schema, actively misinforming the agent about the callable interface. This is worse than adding no parameter info.

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

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

States a specific verb and resource: it diffs risk factors between the latest and prior 10-K/10-Q, returning added/removed/changed items, XBRL changes and a riskDelta summary. This is concrete enough to distinguish it from generic siblings like sec_analyst or search_13f_whale_filings. An agent knows exactly what it produces without opening the schema.

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?

Implies the usage context ('saves reading two full risk sections, often 60k+ characters') and gives a value proposition, but never names when NOT to use it or which sibling (e.g. sec_analyst) to prefer. It also instructs 'Use mode=diff', which is confusing since no such mode selection is framed as a decision. Guidance is present but incomplete.

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 behavioral burden. It does not say whether the call is read-only (implied but unstated), how heavy/long-running the analysis is, whether results are cached or rate-limited, or what the response contains. Only '(Free)' hints at a cost characteristic.

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

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

One front-loaded sentence with no filler; the action and scope come first. The trailing '(Free)' parenthetical is slightly awkward placement but conveys real value, so the sentence remains efficient overall.

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 heavy analysis tool with no output schema and no annotations, the description lists the three analysis dimensions (AI, fundamental, technical), which helps set expectations. But it leaves the return shape, depth, and any constraints unspecified, so an agent still has notable 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?

With a single parameter at 100% schema description coverage, the schema already documents 'symbol' with examples (NVDA, AMZN, PLTR). The description's 'any stock ticker' merely restates the schema's meaning and adds no format or edge-case detail. Baseline 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 states a clear verb (Run) and resource (AI market analysis, fundamental metrics, technical signals) scoped to any stock ticker. An agent can tell this is an analysis/report tool rather than a raw quote lookup. However, it never names or contrasts with siblings like get_stock_quote or run_quant_simulation, which blur its boundary.

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

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

There is no when-to-use guidance beyond 'for any stock ticker'. It does not say when to prefer this over get_stock_quote (simpler quote) or run_quant_simulation (quant modeling), nor any exclusions or prerequisites. The '(Free)' tag hints at cost tradeoffs but is not framed as selection 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 behavioral burden. The only extra info is the cost ($0.10) which is useful. It doesn't state whether the operation is read-only, what permissions are needed, or what a backtest entails (data source, latency, 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?

Two short sentences; the purpose is front-loaded and the price is appended. No filler. It could be more useful but isn't bloated.

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?

A tool with 4 params, a nested allocation object, no annotations, and no output schema. The description omits return values, backtest methodology, data scope, and how results are shaped — significant gaps for a costly simulation tool.

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

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

Schema coverage is 100%, so the schema fully documents all four parameters with descriptions and enums. The description adds little parameter-level meaning beyond pointing at the benchmark by name. Baseline 3 is appropriate given full coverage.

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

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

The description states a verb and resource (backtest a stock strategy over multiple years against a named benchmark). However, 'evaluate_tsunami_strategy' and 'Stock Bloc's high-growth watchlist benchmark' are jargon that don't clarify the tool's core function well, and it doesn't clearly distinguish from the sibling run_quant_simulation.

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 on when to use this vs run_quant_simulation, which appears to be the closest sibling. The agent is left to infer the boundary between 'evaluate strategy' and 'run quant simulation'.

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 behavioral disclosure burden. It usefully identifies the returned data types and that access is free, but it omits freshness, ranking period, and other runtime characteristics for a retrieval endpoint.

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

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

A single front-loaded sentence with no filler. Every clause lists concrete return data, so it is appropriately sized for a simple retrieval tool.

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: one optional parameter, no output schema, and no annotations. The description names the main returned fields well enough for invocation, but it could mention the ranking window or refresh cadence 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?

Schema description coverage is 100%: the sole limit parameter is already documented with its default. The description adds no additional meaning about the parameter, so the 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?

States a specific verb and resource: fetch top ranked Stock Bloc AI agents. The enumerated payload (win rates, alpha returns, badges, active trade recommendations) further distinguishes it, and no sibling tool covers the same leaderboard resource.

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 when-to-use guidance, no alternatives, and no exclusions. The parenthetical '(Free)' is pricing information, not usage guidance, so an agent gets no help deciding when this tool is 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 and does disclose real behavior: a fixed 24-hour freshness window, the specific filing types, an empty-list result when nothing was filed, and a cost signal ('Free' vs a paid inspection route). It omits auth requirements and rate limits, but covers more than the minimum.

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

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

A single front-loaded sentence where every clause earns its place: resource, time window, filing types, access route, empty-state behavior, and cost. No preamble or filler.

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

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

No output schema exists, so the description must convey the return shape, and it does at a high level: a list of filings, empty when nothing was filed, each carrying a paid inspection route. Per-item fields beyond that are left implicit, which keeps it just short of 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 ticker parameter is fully documented in the schema, so baseline is 3. The description's mention of 'the watchlist' adds useful framing about what the ticker filters against but no syntax or format detail 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?

States a concrete resource and scope: 'Real SEC events from the last 24 hours on the watchlist: new 10-K, 10-Q or 8-K filings.' An agent can distinguish this listing tool from analysis siblings like analyze_sec_filing or sec_analyst. It stops short of naming an alternative outright, so a 5 isn't warranted.

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 rather than stated: the 24-hour watchlist window and the pointer to 'the paid route to inspect it' suggest this is the discovery step before a paid inspection call. There is no explicit when-to-use/when-not or named alternative, so guidance remains inferential.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether this is a read-only operation (though it clearly is), what the output looks like, whether it is cached, or any rate limits. It mentions the feeds covered but not the behavior of the check itself or what constitutes a 'stale' flag.

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?

Single sentence, front-loaded with the core action and the specific fields checked, followed by the scope of feeds. Every word earns its place; there is no filler.

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

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

For a zero-parameter, read-only status tool with no annotations and no output schema, the description covers what is checked and which feeds are included. However, it does not specify the return format or what a caller should do with the result, leaving some ambiguity about how to interpret the output.

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?

Parameter count is 0, so baseline is 4. The description provides no parameter information, which is appropriate since there are none. No penalty or bonus beyond baseline.

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

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

States a specific verb and resource: 'Check pipeline data freshness, updated_at timestamps, and stale boolean flags' across three named feeds. This is clear and distinct from siblings like get_stock_quote or search_13f_whale_filings, which retrieve specific content rather than infrastructure status. However, the parenthetical '(Free)' is confusing — it's unclear whether it means the tool is free to use, or that it only covers 'Free' tier feeds, and it distracts from the core purpose.

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

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

The description implies this tool should be used to check data freshness, which suggests its use case, but it never explicitly says when to call it versus alternatives. No exclusions or prerequisites are stated. A user might not know if this should be called before every data request, or only when staleness is suspected.

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 load, and it does disclose two useful behavioral facts: the response includes direct PDF download links and the content is free/unrestricted. However, it never explains what happens when the optional ebookId is omitted (param count is 1, required 0), whether IDs must be discovered elsewhere, or any rate/permission constraints.

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

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

A single front-loaded sentence with no filler or redundancy. The generic word 'information' is the only soft spot, but nothing needs trimming.

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

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

For a one-parameter read tool with no output schema this is adequate but thin: it says what comes back in general terms (info + download links) yet leaves open the no-argument case and how an agent obtains valid ebook ID values.

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% and the single ebookId parameter already carries an example-bearing description, so the schema does the heavy lifting. The description adds nothing about parameter syntax or semantics beyond what the schema shows, which is the baseline-3 case.

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

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

States a specific verb (get) and resource (Stock Bloc financial playbooks), and specifies the payload: information plus direct PDF download links. It is trivially distinguishable from every sibling, none of which touch ebooks, though it never explicitly contrasts itself with 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 when-to-use guidance, no prerequisites, and no mention of alternatives. The '(Free)' tag implies why an agent might reach for it, but nothing tells the agent when this is the right call versus other retrieval 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 carries the full behavioral burden. It usefully discloses a $0.05 cost, which is an important non-schema attribute, but it does not explicitly state that this is a read-only operation, nor does it describe authentication, rate limits, or error 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 fragments with zero wasted words. It front-loads the core purpose and includes the cost as a compact but valuable behavioral signal.

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 read tool with high schema coverage, the description is adequate to support invocation. However, with no output schema and no usage guidance, it does not describe return fields, ordering, or when this historical score data should be preferred over 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?

Schema description coverage is 100%, so all four parameters are already clearly documented in the input schema. The description adds no parameter-level meaning beyond what the schema provides, making the baseline score of 3 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 resource: past values of the 5-factor stock score for a ticker. It is specific and distinct from sibling tools like get_stock_quote or analyze_stock_ai, but does not explicitly name or differentiate itself from those 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 get_stock_quote or analyze_stock_ai. The description only states what the tool returns and its cost, leaving usage context 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, the description carries the full burden and does meaningful work: it discloses cost ($0.01) and that unknown tickers return a free 404, which tells the agent about billing and error behavior. It does not mention auth requirements or rate limits, keeping it short of a 5.

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 dense, front-loaded sentence covering what is returned, the input scope, error behavior, and price. No filler or repetition.

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

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

With no output schema, the description correctly names the return fields (price, 24h change, volume) and covers error and cost behavior. It is nearly complete for a single-parameter quote tool, with only auth/rate-limit context absent.

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 schema already documents the symbol parameter and its examples. The description adds market coverage (US, Hong Kong, India), which is useful but not syntax or format detail beyond the schema; baseline 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?

States a specific resource (current stock price, 24h change, volume) for a ticker, with market scope (US, Hong Kong, India). It is clearly the raw-quote tool among analysis-oriented siblings, though it never names an alternative to differentiate itself explicitly.

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 resource description, and the 'unknown tickers return a free 404' line hints at input expectations, but there is no explicit when-to-use vs when-not guidance or reference to siblings like analyze_stock_ai or get_top_trade_ideas.

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

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

With no annotations, the description carries the full behavioral burden. It does disclose real behavioral constraints — only 'active' theses from 'top-ranked' agents are returned — but says nothing about authentication needs, rate limits, pagination, or the shape of the response, leaving meaningful gaps.

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

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

A single front-loaded sentence with no filler; the key noun phrase ('active high-conviction trade theses and target prices') comes first. The trailing '(Free)' parenthetical is minor but slightly awkward.

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 two-parameter read tool with no output schema, the description covers the core purpose and the scoping notion of 'active' and 'top-ranked'. It stops short of explaining result ordering, pagination, or return structure, which an agent would need to interpret the output confidently.

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 both parameters (limit with default 10, ticker filter) are already fully documented in the schema. The description adds no additional parameter meaning such as ticker format rules or what 'top-ranked' thresholds apply, so the 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?

States a specific verb and resource: retrieves active high-conviction trade theses with target prices. The implicit contrast with submit_agent_trade_idea (submission vs. retrieval) is clear from the verb, but the description never names a sibling to differentiate explicitly.

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 only usage hint is the '(Free)' tag, which signals a pricing tier but not when to use this tool versus alternatives such as analyze_stock_ai or get_agent_leaderboard. No when-to-use or when-not-to-use guidance is provided.

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 behavioral burden, and it does disclose the $0.10 cost and the benchmark used. However, it says nothing about whether the operation is read-only, whether it has rate or data-availability limits, or what the simulation returns, leaving meaningful gaps for a compute-style 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?

Two terse sentences with the core action front-loaded and the price parked at the end; nothing is wasted. The cost fragment and the vague 'multiple years' keep it just below a 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?

With no annotations and no output schema, the description does not explain what a backtest returns (equity curve, metrics, period, units) or any data-window constraints. The parameters are covered by the schema, but the result-shape gap leaves the definition only minimally 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 description coverage is 100%, so the schema already documents tickers, weights (summing to 1.0), and initialCapital. The description adds no parameter meaning beyond that, which matches the baseline 3 when the schema does the heavy lifting.

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

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

States a specific verb (backtest) and resource (a stock strategy over multiple years) plus the benchmark it runs against, which is more than a restatement of the name. It does not name or differentiate itself from siblings like evaluate_tsunami_strategy or analyze_stock_ai, so an agent still has to infer which strategy tool applies.

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

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

There is no when-to-use, when-not-to-use, or alternative-tool guidance. With siblings such as evaluate_tsunami_strategy and analyze_stock_ai available, the description leaves the agent to guess which one fits a given request.

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

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

With no annotations, the description carries the full burden. It does disclose a genuinely useful behavioral trait — the $0.10 cost — which the agent cannot get elsewhere. But it says nothing about read-only safety, return format, result volume, or whether results are ranked/aggregated, so the disclosure is partial.

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?

Short and front-loaded with the resource description, and the cost is placed last where it belongs. But 'Optional limit' is a wasted, misleading clause that does not correspond to any actual input.

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

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

No output schema and no annotations, so the description should explain what comes back — a ranked consensus list? counts? manager breakdown? It does not. Combined with the phantom 'limit' parameter, the definition leaves real gaps for an agent trying to call it correctly.

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

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

Schema coverage is 100% so the 'manager' parameter is documented, giving a baseline of 3. But the description adds negative value by advertising an 'Optional limit' parameter that is absent from the schema, which could lead an agent to pass an invalid argument while never explaining the manager filter's role in this 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?

States a specific resource and angle: stocks that hedge funds and large institutions are accumulating from SEC 13F filings, plus consensus picks. An agent can distinguish this from siblings like analyze_sec_filing or sec_analyst. However, the trailing 'Optional limit' references a parameter that does not exist in the schema, muddying the picture.

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 when-to-use guidance and no routing to alternatives among the many SEC/stock siblings (analyze_sec_filing, sec_analyst, get_top_trade_ideas). The agent must infer from the phrase 'hedge funds and large institutions' alone that this is the 13F-consensus view rather than general filing analysis.

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

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

With no annotations, the description carries the full burden, and it does disclose output contents (added/removed/changed items with quotes, XBRL changes, riskDelta), payload-size option, and cost ($0.05). That is useful context, but it omits mutation/read safety framing and references mode/compact flags absent from the schema, which muddies trust.

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?

Front-loaded with the core question and kept to a few tight sentences; the value framing ('saves reading two full risk sections') is effective. The trailing $0.05 and mode/compact clauses are borderline but brief.

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 3-parameter tool with no output schema and no annotations, the description usefully explains what is returned, so return values are adequately covered. The unresolved references to mode=diff and compact=true, which are not in the schema, leave an agent unable to actually invoke those options, a meaningful completeness 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 ticker/filingType/question semantics are already carried by the schema, giving a baseline of 3. The description adds no parameter-level detail and instead names two non-existent parameters (mode, compact), so it does not improve on 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?

States a specific resource (10-K/10-Q risk-factor diff) and scope (latest vs prior filing), so an agent knows the operation well. However, it never distinguishes itself from the near-identical sibling analyze_sec_filing, leaving a real ambiguity for selection.

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?

'Use mode=diff' is the only usage cue, and it references a parameter that does not exist in the schema. There is no when-to-use vs alternatives guidance and no condition that would route an agent to analyze_sec_filing instead.

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 does disclose an important behavioral trait: the $0.10 USDC x402 pay-per-call cost on Base. It omits whether a registered agent ID is required, what publishing does to leaderboard state, or any rate limits, leaving notable gaps for a write 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?

A single, front-loaded sentence with no filler; the action and purpose lead, and the pricing detail is relegated to a parenthetical. The parenthetical is dense but informative rather than wasteful.

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 an 8-parameter write tool with no annotations and no output schema, the description covers purpose and cost but says nothing about the required agentID/handle registration flow, success behavior, or failure modes (e.g., payment failure). Adequate but with clear gaps.

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

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

Schema description coverage is 100%, so the schema already documents all 8 parameters (ticker, action enum, rationale, agentId, etc.). The description adds no parameter-level meaning beyond confirming a thesis is being submitted, so the baseline 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 states a specific verb ("Publish") and resource ("trade idea or simulated thesis") with a clear goal (compete on the Arena Leaderboard). It implicitly distinguishes itself from read-side siblings like get_top_trade_ideas, though it never names them explicitly.

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

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

There is no statement of when to use this versus alternatives such as evaluate_tsunami_strategy or run_quant_simulation, nor any prerequisites despite register_autonomous_agent being a sibling. The only usage context is the implied goal of competing on the leaderboard.

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