DeltaSignal ATLAS-7

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the behavioral trait 'Subscription-gated,' indicating an access control requirement not covered by annotations. This is useful but minimal; no further details are given (e.g., what happens if not subscribed).

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. It front-loads key qualifiers ('Subscription-gated,' 'semantic,' 'alpha-candidate'). However, it could be slightly more informative without sacrificing conciseness.

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 the tool has 3 optional parameters, an output schema, and is part of a large family of similar tools, the description is insufficiently complete. It does not explain the nature of the output, the meaning of 'alpha candidate,' or how the filters interact. An agent would need additional context to use it 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 has 100% description coverage for all three parameters. The description does not add any new meaning beyond the schema's descriptions. Per the guidelines, baseline 3 is appropriate since 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?

The description 'Subscription-gated semantic alpha-candidate screen' gives a vague sense of the tool's purpose: it provides a list of alpha candidates with semantic filtering and is access-restricted. However, it lacks a clear verb (what action does it perform?) and does not distinguish it from similar sibling tools like 'deltasignal_alpha_opportunities' or 'deltasignal_alpha_signals'.

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 any prerequisites, exclusions, or context about the subscription gate. An agent would have to infer usage from the name 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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds 'subscription-gated', which is a behavioral constraint not captured in annotations. This is useful, but no further behavioral details are 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 extremely concise, a single phrase. It front-loads the key distinction (subscription-gated). However, it may be too terse for full 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?

Given the output schema exists (reducing need to describe returns), and 3 optional parameters, the description is minimal but sufficient for a simple search tool. Missing details about default behavior (e.g., without any params) or 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 has 100% coverage with clear descriptions for cik, limit, and ticker. The description adds no parameter-specific meaning beyond the schema, 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 states 'Subscription-gated archive and history search', clearly identifying the tool as a search for archives and history with an access constraint. It distinguishes from siblings by mentioning the subscription gate, but could be more specific about what kind of content is searched.

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 tool vs alternatives. The 'subscription-gated' hint implies it's for authorized users, but no when-not or comparisons with similar sibling tools like atlas7_recent_history.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's mention of 'Subscription-gated' adds minimal behavioral context. No additional traits like rate limits or side effects are disclosed.

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 short sentence, avoiding fluff, but it is too minimal to convey the tool's purpose effectively. It sacrifices clarity 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?

Despite having an output schema and full schema coverage, the description fails to explain what 'fundamentals surface' means or what kind of data is returned. It is incomplete for a tool with many siblings.

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 parameters. The description adds no extra meaning beyond parameter names, making it adequate but not helpful.

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 'Subscription-gated filing-backed fundamentals surface' is cryptic and doesn't clearly state a specific verb+resource. It fails to differentiate from siblings like atlas7_alpha_candidates or deltasignal_company_fundamentals, which likely return similar 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?

No guidance is provided on when to use this tool versus alternatives. Given many sibling tools, explicit context about when this tool is appropriate (e.g., for retrieving fundamental data from filings) is missing.

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

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

Annotations thoroughly declare the tool as readOnly, idempotent, and non-destructive. The description adds the subscription gate context but does not elaborate on what 'input bundle' entails or any other behavioral traits.

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 but lacks a proper sentence structure. While concise, it sacrifices clarity and completeness.

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 an output schema and rich annotations, the tool is partially contextualized. However, the description fails to explain what the tool returns or when to use it, leaving gaps for an AI 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?

Input schema has 100% coverage with clear descriptions for each parameter (cik, limit, ticker). The description does not add further meaning beyond the schema, meeting the 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?

The description is a noun phrase ('Subscription-gated structured Company Report input bundle') without a verb, making it unclear what action the tool performs. It does not distinguish itself from siblings like atlas7_company_fundamentals or deltasignal_company_report.

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 its many siblings. The description mentions 'subscription-gated' but does not explain when a user would need this input bundle or how it differs from other company report 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?

Annotations already indicate readOnlyHint, idempotentHint true, and destructiveHint false. The description adds value by noting 'Subscription-gated', which informs about access restrictions not covered by annotations.

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

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

The description is a single concise sentence with no wasted words. However, it could be slightly more informative while maintaining 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?

With an output schema present, the description doesn't need to cover return values. However, the minimal description lacks context about what kind of stress data is shown and how it should be interpreted, making it only marginally 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% with each parameter already having descriptions. The tool description does not add additional context beyond what the schema provides, so 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 clearly states it is a view for covenant, debt, and liquidity stress, which aligns with the tool name. However, it does not differentiate from similar tools like 'atlas7_top_stress' or 'deltasignal_covenant_stress', limiting its unique purpose clarity.

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 guidelines are provided about when to use this tool vs alternatives. The description does not mention prerequisites, filtering context, or relationships to sibling tools, leaving the agent without decision 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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds the subscription-gating detail, which is useful behavioral context beyond what annotations provide. No contradictions.

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 short phrase, which is concise but lacks explanatory detail. It is front-loaded but under-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?

With an output schema present and full parameter descriptions, the description is minimally complete but doesn't explain the drilldown output or the meaning of 'lineage' in this context. Adequate but not thorough.

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 five parameters have descriptions in the schema (100% coverage), so the description adds no additional parameter context. Baseline of 3 is appropriate given full schema 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 uses specific terms 'evidence and provenance lineage drilldown', indicating the tool retrieves detailed lineage data. However, it doesn't distinguish clearly from sibling tools like atlas7_lineage_audit or deltasignal_daily_change_evidence, which also deal with evidence/lineage.

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 such as atlas7_lineage_audit. No mention of prerequisites, context, or when not to 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?

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint (safe read operation). Description adds subscription gating and omission of raw SQL, providing extra behavioral context beyond annotations.

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

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

Single sentence that is front-loaded and to the point. Every word adds value. No wasted space.

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?

Despite having an output schema and 100% parameter coverage, the description is minimal. It doesn't explain what a 'signal' is, how this differs from numerous sibling tools, or what the output contains beyond the listed items. An agent may lack sufficient context to decide when to call this 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 description coverage is 100%, so parameters are documented in schema. Description adds no additional detail about parameter usage or semantics beyond what's in the schema, 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?

Description clearly states it provides explanation of fields, evidence requirements, and SQL fingerprint without raw SQL. Verb 'explain' with specific resources. Does not explicitly distinguish from sibling tools like atlas7_semantic_query or atlas7_signal_board, but purpose is 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?

Only mentions 'Subscription-gated' which implies access restriction. No guidance on when to use this tool vs alternatives like atlas7_semantic_query or atlas7_signal_board. Lacks when-not-to-use or prerequisite conditions.

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

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds the 'Subscription-gated' behavioral trait, which is not present in annotations, giving useful context about access restrictions. No contradictions with annotations.

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

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

The description is a single, front-loaded sentence with no redundant words. It efficiently conveys the core function and key constraint.

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 rich annotations and output schema, the description is sufficient for an agent to understand the tool's purpose and access model. It covers the essential context without needing additional details about return 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?

The input schema covers all three parameters with clear descriptions (100% coverage). The description only reiterates 'by ticker or CIK' without adding new semantics. Baseline score of 3 is appropriate since the schema already 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?

The description clearly states the tool retrieves an issuer signal, specifying the input options (ticker or CIK) and the access constraint (subscription-gated). It effectively distinguishes this tool from siblings like atlas7_signal_board or atlas7_quick_ticker_check.

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 obtaining a signal for a specific issuer, but it does not provide explicit guidance on when to use this tool over alternatives or note any prerequisites beyond the subscription gate. The context is clear but lacks exclusions or comparisons.

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

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

Annotations already declare readOnlyHint, idempotentHint, and no destructive action. The description adds 'Subscription-gated,' which implies authorization requirements. However, no further behavioral details are given. The annotations carry the transparency burden, and the description adds marginal value.

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 very concise at four words, which is front-loaded. However, it could be slightly more descriptive without sacrificing brevity. Still, it is efficient.

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 five optional parameters and no usage context, the description is incomplete. The tool could filter by CIK, ticker, etc., but how these interact or what the output contains is not mentioned. Though an output schema exists, the description should provide more overall purpose and usage 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?

All five parameters are documented in the input schema with descriptions. The description does not add any additional meaning or usage context for the parameters. With 100% schema coverage, 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 is vague: 'Subscription-gated calculation lineage audit.' It doesn't specify what 'calculation lineage audit' entails or distinguish it from sibling tools like atlas7_evidence_lineage or deltasignal_atlas7_audit_status. It gives a general idea but lacks specificity.

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 usage guidance is provided. The description does not indicate when to use this tool versus its many siblings, nor does it mention any prerequisites or context for its invocation.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description's 'Subscription-gated' adds a behavioral constraint (access control) not covered by annotations. However, it does not disclose other traits like pagination or what happens when subscription is missing.

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. It is front-loaded with the key access constraint ('Subscription-gated'). No superfluous content.

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 an output schema present and comprehensive annotations, the description does not need to detail return values. However, it does not elaborate on what 'market context' includes, leaving some ambiguity about the tool's output scope.

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 description adds no extra meaning to the parameters beyond what the schema already provides. 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 'Subscription-gated market and instrument overlay context' indicates the tool provides market context with optional instrument filtering, but lacks an explicit verb (e.g., retrieve, get). It distinguishes from many sibling tools which focus on specific signals or reports, but the purpose is somewhat vague.

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 like atlas7_signal_board or atlas7_company_fundamentals. The subscription mention hints at access constraints but does not provide clear use-case scenarios.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds 'Subscription-gated', a behavioral constraint not in annotations, but provides no further details on side effects, rate limits, or auth requirements.

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, very concise, with no redundant information. It earns its place by stating the core purpose and access restriction.

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 the domain and the presence of many sibling tools, the description is too brief. It does not explain what a 'Morning Brief input bundle' contains, nor how the output relates to other tools. Although an output schema exists, the high-level context 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?

The input schema has 100% description coverage for all three parameters. The description does not add additional meaning beyond what the schema already provides, such as the purpose of 'stress_field' or 'signal_filter' in context of the 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 clearly states the tool provides a 'Morning Brief input bundle' and notes it is 'Subscription-gated', indicating access control. However, it does not explicitly differentiate from similar tools like 'deltasignal_morning_brief'. The verb is implicit but the resource is 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?

No guidance is provided on when to use this tool versus alternatives. The description mentions 'subscription-gated' but does not specify prerequisites or compare to sibling tools such as 'deltasignal_morning_brief' or 'atlas7_company_report_inputs'.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, indicating safe, idempotent behavior. The description adds 'subscription-gated', a useful behavioral constraint not covered by annotations. No contradictions.

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 front-loaded with the key feature 'subscription-gated'. However, it is too terse to fully inform usage, missing some necessary detail. Still, it avoids unnecessary verbosity.

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 complexity (3 parameters, output schema, many siblings), the description is insufficient. It lacks explanation of what 'peer ranking' means, how parameters should be used, and guidance on subscription limitations. Annotations help but description gaps remain.

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 documents parameters clearly. The description adds no additional context beyond the schema, hence a 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 states 'peer ranking and relative pressure', which conveys a general purpose. However, it lacks a specific verb and does not distinguish from similar sibling tools like deltasignal_peer_ranking or atlas7_pressure_board.

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. No exclusions, prerequisites, or context are provided, making it difficult for an agent to decide 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?

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral context: it is subscription-gated and currently in MVP state with limited filter functionality (ticker/CIK only). This helps the agent understand constraints beyond what annotations convey.

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 sentences, no waste. The first sentence delivers the core purpose, and the second adds critical MVP context. Information density is high and front-loaded.

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

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

For a simple retrieval tool with 3 optional parameters, output schema, and full annotations, the description is complete. It covers purpose, access gating, current filter capabilities, and MVP status. No missing critical details.

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?

Input schema has 100% description coverage, with clear explanations for ticker, CIK, and limit. The tool description repeats 'ticker or CIK filters' but adds no new semantic meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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

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

The description clearly states the tool is for 'saved watchlist analysis' and specifies that it accepts ticker or CIK filters. It distinguishes from sibling tools by focusing on portfolio watchlist, which is not covered by other ATLAS-7 tools like alpha_candidates or market_context. The mention of MVP and persistence adds clarity on current scope.

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 tool versus alternatives. It mentions 'Subscription-gated' which hints at access control but does not provide context for when to prefer this over other ATLAS-7 tools. No exclusions or alternative recommendations are given.

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

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering most behavioral traits. The description adds one additional detail: 'subscription-gated', which indicates access restriction. It does not contradict annotations.

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

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

The description is a single short sentence, which is concise but lacks structure and key elements. It does not front-load essential information or provide context in a well-organized manner.

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 the tool (optional parameters, many siblings, existence of an output schema), the description is insufficient. It does not explain the board's purpose, what data it returns, or how it differs from similar tools, leaving important gaps for the 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% with clear descriptions for all three parameters (limit, stress_field, signal_filter). The description does not add any meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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

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

The description 'Subscription-gated semantic pressure board' lacks a specific verb indicating what action the tool performs. It reads as a label rather than an explanation, making it unclear whether the tool retrieves, lists, or analyzes data. The name 'pressure_board' is not self-explanatory, and the description does not clarify its output or functionality.

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 its many siblings, such as atlas7_signal_board or deltasignal_pressure_board. The description does not mention context, preconditions, or exclusions, leaving the agent without decision 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?

Annotations already provide readOnlyHint, idempotentHint, etc. The description adds 'subscription-gated', which is a useful behavioral constraint not in annotations. However, it doesn't detail what happens without a subscription or the nature of 'semantic triage'.

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 overly concise (4 words). While not verbose, it sacrifices clarity for brevity. A few more details would improve structure without being 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?

Given the existence of an output schema, return values are covered, but the description fails to explain what 'semantic ticker triage' entails or how the subscription gate works. This leaves gaps for an agent needing to decide when to invoke it.

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 description need not elaborate on parameters. It doesn't mention parameters, which is acceptable since the schema sufficiently describes them.

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 'Subscription-gated semantic ticker triage' gives a general sense of the tool's function but is vague. It doesn't specify the exact action (e.g., retrieve, validate) or how it differs from sibling tools like atlas7_issuer_signal or deltasignal_quick_ticker_check.

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. The description lacks context on prerequisites, subscription requirements, or typical use cases, leaving the agent to infer.

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

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

Annotations already indicate readOnlyHint, idempotentHint, etc. The description adds valuable context about subscription gating and the distinction from DeltaSignal readiness, which are behavioral traits not covered by annotations.

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

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

Two sentences, both necessary and informative. No extraneous text. The first sentence states the core purpose, and the second adds relevant contextual distinction and gating info.

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 simple schema and rich annotations, the description covers purpose, gating, and sibling distinction. The output schema likely explains return values, so completeness is high, though a brief note on what 'readiness' entails would improve it.

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 only parameter, 'limit', is fully described in the schema with min/max and a description. The tool description does not add additional semantics beyond that, so a baseline score is appropriate.

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

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

The description clearly states the tool provides 'semantic readiness and entitlement status' for ATLAS-7, and distinguishes it from the existing DeltaSignal readiness via x402. However, it does not define what 'readiness' means in terms of output, which is a minor gap.

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 mentions the alternative DeltaSignal readiness and the subscription requirement, but does not explicitly state when to use this tool versus other atlas7 tools or provide a comprehensive when-not-to-use scenario.

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

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds only 'Subscription-gated' which hints at access control but does not disclose behavioral traits like data freshness, pagination, or rate limits. The description adds no value beyond annotations.

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

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

The description is only five words, which is too short to be informative. While brevity is valued, this lacks essential details and cannot be considered well-structured or front-loaded with important information.

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

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

For a tool that returns historical issuer trajectory data, the description is incomplete. It does not explain 'point-in-time' meaning, data recency, or what the trajectory contains. Even with an output schema, the description should add context about the nature of the data.

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

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

Schema coverage is 100%, with all three parameters (cik, limit, ticker) described. The tool description does not add any additional meaning or constraints beyond the schema, 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 'Subscription-gated recent point-in-time issuer trajectory' does not contain a clear verb (e.g., 'retrieve', 'list') and the noun 'trajectory' is ambiguous. It fails to distinguish the tool from sibling tools like atlas7_company_fundamentals or atlas7_issuer_signal.

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. There is no mention of prerequisites, typical use cases, or circumstances where a sibling 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?

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds behavioral context: 'Return ATLAS evidence envelopes only; raw SQL is never returned' and mentions subscription gating. This provides additional transparency beyond annotations.

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

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

The description is extremely concise at two sentences. It front-loads the key constraint (subscription-gated) and the output type, with 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?

Given the existence of an output schema (not shown but present), the description does not need to explain return values. It covers the main behavioral aspects and constraints. However, it could mention that it is a semantic query tool for structured evidence retrieval, which is implied but not explicit.

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%, meaning all 6 parameters have descriptions in the input schema. The tool description does not add any extra meaning beyond what the schema already provides, so 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 it is a 'governed semantic query' that returns 'ATLAS evidence envelopes only'. It identifies the tool as a query tool within the Atlas7 suite. However, it does not explicitly distinguish itself from sibling tools like atlas7_alpha_candidates or atlas7_archive_search, which are more specialized.

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 mentions 'Subscription-gated' implying a requirement for use, but does not provide explicit guidance on when to use this tool versus alternatives. The context of sibling tools suggests it is a general-purpose query, but no direct exclusions or when-not-to-use advice is given.

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

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds 'subscription-gated' but does not explain implications (e.g., behavior if unsubscribed). No mention of data freshness, order, or pagination. Adds minimal value beyond annotations.

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

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

Extremely concise (4 words), front-loaded, but at the cost of clarity. Every word should earn its place; here, 'subscription-gated' and 'latest issuer' add some value but overall description is too brief to be adequately 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?

Despite rich annotations and output schema, the description fails to explain what the tool outputs (list of signals? fields?), how 'subscription-gated' works, and how it differs from similar tools. Agents need more context to select 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 descriptions cover all 3 parameters (100% coverage) with clear meanings. The tool description adds no extra insight on parameters, so 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?

Description is vague: 'Subscription-gated latest issuer signal board' lacks an action verb (e.g., list, get) and does not differentiate from siblings like atlas7_issuer_signal or atlas7_pressure_board. It implies a board of signals but does not specify what the tool returns.

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 siblings. Does not mention scenarios, prerequisites like subscription, or exclusions. Sibling list is large but no differentiation 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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering safety. The description adds 'subscription-gated', a critical behavioral trait not in annotations. No contradictions.

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 sentence that is concise and front-loaded. It conveys the core purpose and a key constraint (subscription-gated) without waste.

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 output schema exists and annotations cover safety, the description provides sufficient high-level context. It notes the gated nature and the domain (theme, concept, taxonomy) for a tool with 4 optional parameters.

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 parameters. The description adds no additional parameter meaning beyond what's in the schema, meeting baseline expectation.

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 specific resource nouns (theme, concept, taxonomy) and the verb 'discovery' implies exploration. It distinguishes from sibling tools like atlas7_semantic_query. However, the verb could be more definitive (e.g., 'search' 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 mentions 'subscription-gated' indicating a usage constraint, but provides no explicit when-to-use or alternatives among the many sibling tools. Usage context is implied by the tool name and 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?

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, so the tool is safe. However, the description adds only 'Subscription-gated', which is a business constraint, not behavioral. It does not explain what 'semantic' means or any data returned.

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

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

The description is concise (one sentence), but at the cost of informativeness. It is not overly verbose, but fails to earn its place by providing necessary detail.

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 presence of an output schema, return values are covered, but the description lacks explanation of the ranking semantics, how it differs from sibling tools, or any computation context. For a tool with many similar siblings, more completeness is needed.

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 each parameter (limit, stress_field, signal_filter) already has a description. The tool description adds no additional parameter context, 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?

Description 'Subscription-gated semantic top-stress ranking' is vague. It states it's a ranking but does not specify what 'stress' refers to or what 'top-stress' means. It fails to distinguish from similar sibling tools like 'deltasignal_top_stressed' or 'atlas7_covenant_stress'.

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 usage guidelines provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites or exclusions.

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

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description reinforces this and adds specific behavioral details: a single HTTPS read, no side effects, and no handling of wallets or orders. No contradictions.

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

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

The description is concise at 8 sentences, front-loaded with purpose, then parameter details, then behavior. Every sentence contributes meaning 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?

Given the tool's complexity (7 parameters, no required params, complete schema coverage, annotations, and output schema), the description covers purpose, parameter usage, behavior, and limitations. It is comprehensive for an AI agent to select and invoke correctly.

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

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

With 100% schema description coverage, the baseline is 3. The description adds value by explaining the limit range, source_date replay, and how each filter narrows results. It also provides usage context for include_funds and issuer_type.

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

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

The description clearly states the tool's purpose: to rank the DeltaSignal issuer universe by alpha score. It specifies the output fields and distinguishes it from siblings by emphasizing its read-only screening nature and specific parameter options.

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 guidance on when to use parameters like include_funds and issuer_type, and notes the default behavior. It also cautions that high scores are drilldown candidates, not conclusions. However, it does not explicitly contrast with sibling tools like deltasignal_alpha_signals.

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

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

Annotations already indicate readOnlyHint, idempotentHint, destructiveHint. Description adds behavioral details: performs one HTTPS read, no destructive side effects, does not change board scoring, payments, wallets, files, or account state. No contradiction.

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?

Description is concise at about 8 sentences, front-loaded with purpose, and structured with parameter details and usage guidance. 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?

Given 4 parameters and an output schema (not shown), the description fully covers purpose, behavior, parameter details, and usage scenarios. It is comprehensive for the tool's complexity.

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

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

Schema coverage is 100% with descriptions. The description adds semantic context beyond schema: e.g., limit is 1-100 for bounded samples, source_date replays a known slice, issuer_type narrows audit, include_rows should be used only for explicit debugging.

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 is a read-only diagnostic tool to explain why the alpha-opportunity board includes, excludes, or demotes rows. It specifies the return summaries and distinguishes from sibling tools like deltasignal_alpha_opportunities and deltasignal_alpha_sweep.

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?

Explicitly provides when to use: after deltasignal_alpha_opportunities or deltasignal_alpha_sweep when the user asks about missing rows, exclusions, demotions, or safety of summarizing. Also gives example scenarios.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds operational details: 'performs one HTTPS read, has no destructive side effects, does not trade, does not store user data, and does not handle wallet secrets.' This goes beyond annotations but some context (e.g., idempotency) is already hinted.

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

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

Three tightly-written paragraphs with front-loaded purpose. Every sentence earns its place: no fluff, clear structure covering purpose, parameters, behavior, and usage guidelines.

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 complexity (alpha signals, optional replay date, many siblings), the description covers all necessary aspects: return content, parameter usage, behavioral safety, and guidance for alternatives. Output schema exists, so return values need not be detailed.

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 baseline is 3. Description adds meaning: explains ticker normalization and that source_date should be used 'only to replay a known historical DeltaSignal slice,' which clarifies its purpose beyond format constraints.

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 ('retrieve') and resource ('DeltaSignal ATLAS-7 alpha signals for one crypto public company ticker'), and differentiates from siblings by mentioning specific alternatives later (covenant_stress, company_fundamentals).

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?

Explicitly states when to use ('research triage on supported public-company tickers'), when not to use ('do not pass crypto asset symbols unless they are listed public-company tickers'), and provides specific alternative tools (readiness, covenant_stress, company_fundamentals).

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?

Description adds significant behavioral context beyond annotations: it explains the tool performs three internal HTTPS reads, is idempotent and read-only, has no side effects, never calls issuer-level tools, and preserves partial results on failure. This aligns with and enriches the annotations (readOnlyHint, idempotentHint, destructiveHint).

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 well-structured with front-loaded purpose. It includes all necessary details without excessive verbosity. Minor redundancy (e.g., 'read-only' mentioned twice) could be trimmed, but overall it is concise and organized.

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 complexity (composite, internal calls, partial failure) and the availability of output schema, the description provides complete guidance: what it does, how it works internally, when to use it, what parameters to avoid, and how to interpret the result as a screen requiring further drilldown. No 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 coverage is 100%, so baseline is 3. Description adds value by clarifying that only 'compact' is accepted for output_mode and explicitly forbids passing other parameters (limit, offset, etc.) even though they are not in the schema. This prevents misuse.

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 is a read-only composite workflow for alpha screening across the DeltaSignal issuer universe, specifying the internal call plan (readiness, alpha_opportunities, daily_changes). It distinguishes from sibling tools like deltasignal_alpha_opportunities by noting it enforces a preset call plan and does not accept issuer-level filters.

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?

Explicit usage guidance: 'Use it when the user asks for alpha opportunities, opportunity sweep, clean alpha board, or names worth follow-up research.' It also clearly states which parameters must not be passed (limit, offset, ticker, source_date, issuer filters) because the tool owns them internally. This helps the agent avoid incorrect invocations.

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 significantly adds to the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) by detailing specific behaviors: it resolves article objects, compares filing evidence, marks missing evidence, returns eight thesis-map sections, and explicitly states what it does not do (call Grok, invent evidence, mutate storage, treat TripCodes as SEC identities). This provides comprehensive transparency beyond the structured annotations.

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

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

The description is front-loaded with the core use case and contains multiple sentences that each add unique information (purpose, parameter hints, behavioral guarantees, limitations). It is well-structured and avoids redundancy, though the length is justified by the tool's complexity and number of parameters. It could be slightly tightened without losing 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?

Given the tool's complexity (25 optional parameters, output schema present, rich annotations), the description covers all necessary aspects: what the tool does, when to use it, key parameters, behavioral guarantees, and what it does not do. The presence of an output schema reduces the need to describe return values, and the description fills remaining gaps 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?

Schema description coverage is 100%, so the baseline is 3. The description highlights the most important parameters (article_tripcode, tripcode, prior_article_tripcodes, linked_xbrl_tripcodes, filing_tripcodes, ticker) and mentions the special HUT behavior. This adds context but does not explain individual parameter meanings beyond what the schema already provides. The description adds marginal value.

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

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

The description clearly states the tool's purpose: it generates a thesis map from a DeltaSignal article TripCode. It specifies the trigger ('when a subscriber gives... an article TripCode and asks for the thesis map') and the resource (the article). This distinguishes it from sibling tools like deltasignal_alpha_opportunities or deltasignal_compare_article_to_filing_evidence, which serve different functions.

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 explicit context for when to use the tool: when a subscriber requests a thesis map given an article TripCode. It identifies the primary parameters (article_tripcode or tripcode) and optional ones (prior_article_tripcodes, linked_xbrl_tripcodes, filing_tripcodes, ticker). It also mentions a special case for HUT. However, it does not explicitly state when not to use this tool or suggest alternatives, which would improve 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?

Annotations already indicate readOnlyHint, idempotentHint, destructiveHint. The description reinforces these and adds specific context: no destructive side effects, does not run the audit, mutate data, or access raw issuer evidence. This adds value beyond annotations.

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

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

The description is a single well-structured paragraph, front-loaded with the main purpose. It is concise but thorough, using each sentence to add essential information 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?

Given the presence of an output schema (so return values are covered there) and rich annotations, the description fully covers purpose, usage, and behavioral traits. No gaps remain for this simple parameterless 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?

Input schema has no parameters, and description explicitly states 'Parameters: none.' With 0 parameters, the baseline is 4, and the description adds no extra param detail but is clear about absence.

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

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

The description clearly states the tool checks ATLAS-7 audit health, reads the latest audit summary from Azure Blob, and lists the reported fields. It distinguishes itself from sibling tools by being a read-only status check rather than running the audit or accessing raw 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?

Explicitly states when to use it: 'Use this before trusting historical ATLAS-7 surfaces' and 'when an operator asks whether the nightly audit is current.' Also clarifies it does not run the audit or mutate data, providing clear usage boundaries.

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

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

Beyond annotations (readOnlyHint, destructiveHint, idempotentHint), the description adds that it assembles from precomputed surfaces and performs no wallet/settlement/trading actions. This provides useful behavioral context without contradicting annotations.

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

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

Every sentence in the description serves a purpose: purpose, component list, parameter summary, behavioral note, and usage hint. It is front-loaded with the most important information and contains 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?

The description covers purpose, usage, parameters, and behavior. With an output schema present, it doesn't need to detail return structure. It could mention pagination more explicitly, but the parameter descriptions handle that.

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

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

Schema coverage is 100% with good descriptions. The tool description adds value by explaining how parameters work together (e.g., source_date replays a slice, range for paging, ticker/CIK narrowing, mode behavior). This enhances understanding beyond individual schema descriptions.

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 returns the complete ATLAS-7 calculation bundle for an issuer and source_date, and lists the components. It differentiates itself from sibling tools like deltasignal_atlas7_companyfacts_history and deltasignal_atlas7_point_in_time_history by focusing on the full bundle.

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 explicitly says to use this tool when needing the complete calculation bundle for historical report rendering, and warns against mixing latest-only fields. It provides context but does not list alternatives or when not to use, though that's partially mitigated by sibling names.

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?

Description adds value beyond annotations by stating 'it performs no writes, has no destructive side effects, and never returns the raw facts_payload' and advises how to drill down. This aligns with annotations (readOnlyHint, idempotentHint, destructiveHint) and provides actionable guidance.

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?

Description is concise (4 sentences), front-loaded with purpose, then details, then parameter info, then behavioral notes. Every sentence adds value with no redundancy.

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

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

Given output schema exists, description does not need to explain return values. It covers key behaviors, parameter usage, universe size, and drill-down guidance. Complete for a retrieval tool with rich annotations.

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 baseline is 3. Description adds context by listing parameters like source_date, ticker/cik, limit, offset with defaults and behavior (e.g., 'limit defaults to 25 and is capped at 250'), enhancing usability beyond schema descriptions.

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?

Description clearly states verb 'retrieve', resource 'compact SEC CompanyFacts/XBRL materialization rows', and scope 'crypto public-company universe or a specific ticker/CIK'. It distinguishes from siblings by specifying usage for 'Mirror Pulse or ATLAS-7 historical joins' and mentions '215 crypto companies'.

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 provides explicit usage context: 'Use this for Mirror Pulse or ATLAS-7 historical joins when you need the compact issuer-level CompanyFacts inventory'. It does not explicitly mention when not to use or name alternative tools, but the context is clear enough for selection.

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 explicitly lists behavioral traits: read-only, idempotent, no destructive side effects, and what it does NOT do (fetch live data, run calculations, place trades). This adds significant value beyond the annotations (readOnlyHint, idempotentHint, destructiveHint) by clarifying boundaries.

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

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

The description is concise (4 sentences), front-loads the purpose, and efficiently covers purpose, behavior, and parameters with 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?

Given that an output schema exists, the description does not need to detail return values. It adequately explains the four levels and their possible states, and covers all key aspects for a tool with 6 optional parameters and no required inputs.

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

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

Schema coverage is 100% with detailed descriptions for all 6 parameters. The description merely lists parameter names and mode options, adding little new information. Baseline 3 is appropriate as the schema already provides full 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 uses a specific verb ('determine') and resource ('ATLAS-7 four-level layers'), clearly stating the tool's purpose. It also distinguishes itself from siblings by noting it generalizes the AI10/Tech100 engine across the legacy issuer universe, which sets it apart from other atlas7 tools.

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

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

The description provides clear context ('for one issuer or a paginated issuer universe') and states what the tool does without misleading. However, it does not explicitly say when to use this over alternatives or exclude specific use cases, though the context is sufficient for an agent to infer 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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context beyond annotations: it performs one HTTPS read, no NLP, no trades/wallets/settlements. This additional detail enhances transparency without contradicting the annotations.

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

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

The description is a single paragraph of five sentences, front-loaded with purpose and usage. Every sentence adds necessary detail without redundancy. It is efficient and well-structured for an AI agent 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 high parameter count (8), optional params, and existence of output schema, the description is quite complete. It covers purpose, usage context, mode selection, and safety. It does not detail output semantics, but that is covered by the output schema. Minor gaps: exact pagination limits are in schema but not repeated, and difference from sibling companyfacts_history tool is implicit but clear.

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 restates parameters and adds usage advice for mode (compact vs full), but does not significantly augment the meaning beyond what the schema provides. The added guidance on mode selection earns it a 3 rather than a 2.

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 is for retrieving daily ATLAS-7 CompanyFacts-derived factor rows keyed by as_of_date, with emphasis on point-in-time safety and lookahead flags. It distinguishes itself from siblings by being a structured history tool specific to factor rows, and the read-only nature is explicit.

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 specifies exactly when to use this tool: for Mirror Pulse, backtests, or agents needing daily ATLAS-7 factor history. It provides mode recommendations (compact by default, full for audit pages). However, it does not explicitly mention alternatives or when not to use it, though the context of siblings makes the differentiation clear.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds operational details: 'it performs one HTTPS read, has no destructive side effects, and does not apply the latest ATLAS snapshot retroactively across history.' This adds value beyond the annotations without contradiction.

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 paragraph that efficiently communicates purpose, parameters, and behavior. It is front-loaded with the main action. While compact, it includes necessary detail 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?

Given the output schema exists (not shown but indicated), the description still lists return fields: 'debt, crypto fair value, BTC holdings, stress, risk tier, live-price fields, quality flags, and provenance.' This covers the context needed for an agent to understand the tool's output. The description is complete for the tool's complexity.

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

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

The input schema has 100% coverage, but the description adds context by summarizing parameters and stating defaults and caps: 'ticker is required; source_date_from and source_date_to bound the inclusive ATLAS source-date range; limit defaults to 500 and is capped at 2000; offset paginates the dated series.' This goes beyond the schema's individual descriptions.

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 retrieves 'historical ATLAS-7 covenant and stress series for one crypto public company ticker', using specific verbs and resources. It distinguishes from siblings by mentioning unique use cases like mNAV backtests and Mirror Pulse joins, which are not covered by similarly named tools such as deltasignal_atlas7_point_in_time_history.

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 explicit use cases: 'when the user needs historical ATLAS data, MSTR/Strategy time series, mNAV backtests, Mirror Pulse joins, or dated stress/risk snapshots.' It does not explicitly mention when not to use or name alternative tools, but the context is clear enough for an agent to decide.

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 reinforces the annotations (readOnlyHint, idempotentHint, destructiveHint) by stating it is read-only and idempotent with no destructive side effects. It adds behavioral context not in annotations: it does not fetch live data or place trades. No contradiction with annotations.

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

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

The description is two sentences: the first states purpose, the second lists parameters and behavior. It is front-loaded with the most important information and contains no redundant 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?

Given the complexity (8 optional parameters, output schema exists, sibling tools), the description covers the key retrieval purpose, negative behavior, and parameter categories. It does not need to detail return values due to output schema. It could briefly mention pagination behavior, but limit and offset are in schema.

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

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

Schema description coverage is 100%, so all parameters are documented. The description provides a helpful summary grouping related parameters (e.g., source_date or source_date_from/source_date_to, mode=compact|full). This adds value beyond the schema by giving an overview of filtering capabilities.

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 retrieves Coinbase INTX perp market-factor history from persisted recorder evidence. It specifies the verb 'retrieve' and the resource 'calculation history', distinguishing it from sibling tools like deltasignal_coinbase_perp_factors or deltasignal_coinbase_perp_constituents.

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 explicitly states what the tool does not do: it does not fetch live exchange data, place trades, or mutate state. This helps the agent avoid misuse. However, it does not directly compare with sibling tools or provide explicit when-not-to-use guidance, though the purpose is already differentiated.

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 reinforces annotations by stating 'read-only and idempotent with no destructive side effects'. It adds value by explaining the data is persisted registry rows with evidence boundaries, not live constituents. No contradictions.

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

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

The description is concise at 5 sentences, front-loaded with purpose and usage. Each sentence adds value: purpose, return type, parameters, behavior. No fluff.

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?

Output schema exists, so return details are covered. The description covers purpose, parameters, behavior, and data nature. Minor gaps: pagination logic and date range combination not fully explained.

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 baseline is 3. The description lists parameters and adds context like 'grouped constituent registries' and 'compact|full' mode, but does not significantly add meaning beyond schema.

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

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

The description clearly states the tool retrieves persisted constituent registries for one Coinbase thematic or index perp product, with specific examples. It distinguishes from siblings by emphasizing it returns curated overlays grouped by source date, not live exchange-native APIs.

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 explicitly says 'use this read-only tool to retrieve' and clarifies it does not fetch live data or place trades. It provides clear context for when to use, but does not explicitly list alternatives or when-not-to-use scenarios.

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

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description reinforces these by stating 'read-only and idempotent with no destructive side effects' and adds context about not fetching live exchange state or writing recorder artifacts. This adds significant value beyond the annotations without contradiction.

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 consists of exactly two sentences, front-loaded with the purpose and usage guideline. The second sentence efficiently enumerates parameters and behavior. No filler or 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?

Given 8 parameters with 100% schema coverage, full annotations, and an output schema, the description provides sufficient context. It explains the tool's purpose, scope (single product), input parameters, and expected output, making it fully actionable for an AI 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 baseline is 3. The description adds value by summarizing parameters (required product, optional source_date, source_date_from/to, underlying_ticker, mode, limit, offset) and explaining how they affect the output (e.g., mode=compact|full, factor rows returned). It provides context beyond bare schema fields.

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 precisely states the tool reads persisted Coinbase INTX market-factor history for one perp product, listing specific output fields (factor rows, deltas, quality state, optional full market inputs or lineage). This clearly distinguishes it from sibling tools like perp_calculation_history or perp_constituents, though explicit differentiation is absent.

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 explicitly states when to use the tool ('when the user wants persisted Coinbase INTX market-factor history for one perp product'). It also clarifies what it does not do (fetch live state, write artifacts), providing clear context. However, it does not specify when not to use it or suggest alternatives among siblings.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds value by specifying what the tool does not do (create factors, reconstruct depth, override rows) and explaining the conversion process, providing behavioral context beyond the structured fields.

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

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

The description is concise with two short paragraphs. The first sentence front-loads the purpose. Every sentence adds value, and there is no wasted text. It is appropriately 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?

Given the tool has 6 parameters, an output schema, and annotations, the description covers purpose, behavior, and parameter usage adequately. It explains what the tool transforms and preserves, making it complete for an agent to invoke correctly.

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

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

Schema coverage is 100%, so baseline is 3. The description lists parameters and notes defaults/caps (limit) but does not add significant new meaning beyond what the schema already provides. It organizes the parameters helpfully but does not compensate beyond the 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?

The description clearly states the tool retrieves the market SPECTRA field map for one Coinbase INTX perp product, using specific verbs and resource identification. It distinguishes from siblings by being Coinbase perp-specific and explaining the internal conversion process.

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 indicates it is a read-only tool for retrieving SPECTRA field maps but does not explicitly state when to use it over alternatives or provide exclusions. It implies usage context via the 'read-only' and 'does not create factors' statements but lacks direct comparisons to sibling 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?

Annotations already declare readOnlyHint and idempotentHint. The description adds valuable behavioral context: 'performs no live exchange fetches, order placement, or settlement flows', which goes beyond annotations and clarifies safety for an agent.

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: two sentences, no wasted words. The first sentence clearly states purpose and output, the second lists parameters and behavioral guarantees. It is front-loaded 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 8 optional parameters, read-only behavior, and presence of an output schema, the description covers the core functionality and return fields. Minor omissions like error handling or rate limits are acceptable given the safety annotations. The description is complete enough for an agent to use the tool 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?

Schema description coverage is 100%, and the description summarizes parameters (filters, mode, pagination) but does not add meaning beyond what the schema provides. The description lists them but offers no additional context or constraints.

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 specific verbs and resources: 'rank Coinbase INTX perp products by the latest persisted market_alpha row per product'. It clearly distinguishes this tool from siblings like deltasignal_coinbase_perp_factors and deltasignal_peer_ranking by specifying the ranking and board output.

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 ranking and lists parameters, but does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions or alternative tools are mentioned, leaving the agent to infer context from the name and sibling list.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds that it performs one HTTPS read, has no destructive side effects, and does not modify SEC data, accounts, files, or wallets. No contradiction, and extra context reinforces safety.

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 well-structured: purpose first, then parameters, then behavior, then usage guidance. It is slightly verbose but each sentence adds value. Could be tightened but still effective.

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 covers all important aspects: what data is returned, parameter details, behavior (read-only, idempotent), usage context, and sibling differentiation. Output schema exists so return format is documented. Fully adequate.

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

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

Schema coverage is 100%, so baseline is 3. The description adds nuance by explaining that include_segments and include_related_party return availability metadata even when facts are not populated, and that period is optional with default latest filing. This goes beyond schema.

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

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

The description clearly states the tool retrieves SEC XBRL-backed fundamentals for one crypto public company ticker. It enumerates specific data returned (filing period, identifiers, core financial values, provenance, optional containers), and distinguishes from sibling tools like alpha_signals and covenant_stress.

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?

Explicitly specifies when to use this tool (revenue, net income, assets, cash, liabilities, equity, SEC filing context, fact provenance) and when to use alternatives (alpha_signals, covenant_stress). No 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?

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds specific behavior: performs six internal HTTPS reads, rejects invalid tickers before fan-out, preserves partial results on leg failure. No contradiction with annotations.

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

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

Description is a single dense paragraph that front-loads purpose and then details parameters and behavior. It is efficient, though slightly long; every sentence adds value.

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

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

Given the tool has an output schema (not shown) and detailed input schema with 100% coverage, the description covers behavior, usage, parameter details, and edge cases (e.g., partial results). It is fully complete for an AI agent to use 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 baseline is 3. Description adds minor context: ticker normalization to uppercase, optional parameters listed, SPECTRA inclusion condition. This adds some value but does not significantly deepen 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 it is a composite workflow tool for the default full single-issuer DeltaSignal ATLAS-7 company report. It specifies the scope (single issuer, full report) and implicitly distinguishes from lower-level sibling tools for custom drilldowns.

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?

Explicitly states when to use: for report, deep dive, issuer brief, diligence package, or when Morning Brief rows need explanation. Also says to use low-level tools only for custom drilldowns, providing clear guidance on alternatives.

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

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable context beyond annotations: 'no destructive side effects, does not mint official SEC identity, does not infer filing evidence from prose, and does not call wallets or x402 settlement.' This fully discloses behavioral traits.

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 paragraph but front-loads the purpose and key behaviors. It is concise given the complexity (18 parameters). However, structure could be improved with bullet points or separation of parameter notes and behavior notes, but the current form avoids verbosity.

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 18 parameters and an output schema (true), the description covers the main use case (HUT MVP), return value composition, and constraints. It lacks guidance on error handling or behavior when article_tripcode is omitted, but overall it provides sufficient context for an AI agent to invoke correctly.

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

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

Schema coverage is 100% with descriptions for all 18 parameters. The description adds value by summarizing default behavior (e.g., ticker=HUT loads default pack, filing_tripcodes optional). While it doesn't explain each parameter in detail, it complements the schema well.

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

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

The description clearly states the tool's purpose: 'compare a TF-SUB article node against resolved TF-XBRL filing evidence objects'. It uses specific verb-resource pairing and distinguishes from siblings by specifying read-only comparison. The mention of HUT MVP default behavior adds clarity.

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 outlines parameters and defaults (article_tripcode optional, filing_tripcodes for one or more objects, ticker=HUT loaded default pack). It explains idempotent and local behavior. However, it does not explicitly exclude use cases or contrast with sibling comparison tools like 'deltasignal_compare_claim_to_evidence', which would improve 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?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's 'read-only with no destructive side effects' is consistent. Additional value comes from stating the return categories ('confirmed, weakened, unresolved, or new_claim') and explicitly noting it does not 'invent evidence', which is beyond the annotation metadata.

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 (approximately 40 words) with no filler. It front-loads the primary purpose and read-only nature, then efficiently covers parameter combinations and behavior. Every sentence is informative and earns its place.

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 output schema exists, the description does not need to detail return types, but it still lists the outcome categories. It covers purpose, parameter guidance, behavioral safety, and expected results. With 14 optional parameters and high schema coverage, the description provides sufficient context for an agent to decide when and how to invoke the tool.

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

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

The input schema has 100% parameter description coverage, so each parameter is individually documented. The description adds meaning by grouping required-optional patterns ('pass claim_text or query plus river_tripcode or issuer'), which helps the agent understand valid parameter combinations. This spatial guidance adds value beyond the isolated schema descriptions.

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 a claim to River claim records and evidence refs, uses a specific verb (compare), and specifies the resource (claim vs River records). It also lists possible outcomes (confirmed, weakened, unresolved, new_claim), making the purpose unambiguous. While sibling differentiation is not explicit, the other 'compare' sibling ('deltasignal_compare_article_to_filing_evidence') targets different sources, so the scope is distinct enough.

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 advises this is a 'read-only tool' and suggests parameter combinations ('pass claim_text or query plus river_tripcode or issuer'), which gives some usage context. However, it does not specify when to avoid this tool or mention alternative tools like 'deltasignal_search_by_claim' or 'deltasignal_compare_article_to_filing_evidence', leaving the agent to infer usage boundaries.

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

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds context: 'it performs one HTTPS read, has no destructive side effects, and does not change filings, portfolios, wallets, or account state.' This reinforces safety and provides operational detail.

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 well-structured, starting with purpose and mode selection, then parameters, behavior, and alternatives. It is front-loaded and informative, though slightly verbose. Every sentence contributes meaning.

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 (10 parameters, two modes, output schema exists), the description thoroughly covers both modes, explains filtering, mentions output fields, and lists alternatives. It is complete for an agent to use correctly.

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

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

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining that ticker selects detail mode and that without it, list-mode filters apply. It provides ranges (min_stress 0-100) and usage tips ('Use 10-25 for concise screens'). This exceeds 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?

The description clearly states it is for ATLAS-7 covenant stress analysis on crypto public companies, with specific verb 'analyze' implied. It distinguishes two modes (detail with ticker, list without ticker) and mentions specific outputs. Among siblings, it differentiates itself by naming alternatives like top_stressed and peer_ranking.

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 explicitly says when to use each mode and provides alternatives: 'Use top_stressed for the default ranked universe, peer_ranking for relative peer context, and alpha_signals when the user asks for opportunity or edge rather than covenant stress.' This is excellent 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?

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. The description adds valuable context: 'read-only and idempotent; it performs one HTTPS read... has no destructive side effects, and never infers covenant breach, default risk, insolvency, liquidity crisis, or trade direction unless returned by evidence.' This goes beyond annotations.

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

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

The description is a single dense paragraph that front-loads purpose. Every sentence serves a purpose; it is not overly long. Some structuring could improve readability, but it is concise enough for the content.

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 annotations cover safety, an output schema exists (not detailed here), and parameters are documented, the description is largely complete. It covers purpose, usage, behavior, and parameter mapping. It does not detail output format, but that is handled by the output schema.

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

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

Schema coverage is 100% with descriptions for each parameter. The description mentions parameters (ticker required, date optional, style options) but adds only marginal value, such as explaining style affects tone/density. 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 explicitly states it is a 'premium read-only Natural Language tool' for 'ticker-specific covenant stress evidence explained in human-readable Markdown.' It specifies the data sources (ATLAS-7 covenant, leverage, etc.) and differentiates from sibling tools like 'deltasignal_covenant_stress' which likely returns structured 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 clearly says 'Use this premium read-only Natural Language tool when the user wants ticker-specific covenant stress evidence explained in human-readable Markdown.' It implies alternatives exist (e.g., structured data tools) but does not explicitly state when not to use or provide exclusions. The sibling list provides context for differentiation.

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

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

Annotations already indicate readOnlyHint, idempotentHint, and no destructive effects. The description adds value by stating it performs 'one internal daily-changes read, filters evidence for one issuer/change, and has no destructive side effects.' No contradiction.

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 four sentences, front-loaded with purpose and usage, then parameters, then behavior. Every sentence provides essential information without fluff.

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 presence of an output schema and rich annotations, the description covers all necessary aspects: purpose, usage constraints, parameter behavior, and side-effect profile. It is complete for the tool's complexity.

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 description reiterates key details: ticker or cik required, source_date optional, limit defaults to 100 and capped at 250, offset for pagination. This adds practical context beyond the schema.

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

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

The description clearly states the tool is a 'read-only drilldown tool' for explaining why an issuer or CIK was flagged in daily changes. It distinguishes from sibling tools like deltasignal_daily_changes and explicitly defines its narrow scope.

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?

Explicitly states 'only when the user asks why one issuer or CIK was flagged in daily changes' and warns against using for 'routine monitoring, Morning Brief, or Alpha Sweep unless the user explicitly asks for proof.' This provides clear when-to-use and when-not-to 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?

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds beyond this by specifying it performs one HTTPS read and has no side effects on notifications, files, accounts, or wallet state, enhancing 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 paragraph that covers purpose, content, usage, and behavior without redundancy. It is concise and front-loaded with the key usage instruction.

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 no parameters, the description fully covers what it does, its outputs, usage context, and behavior. The presence of an output schema further supports completeness.

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?

There are no parameters, and the description explicitly states 'Parameters: none'. This is clear and adds value beyond the schema, which already documents no 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 identifies the tool as a monitoring tool for daily change snapshots, listing specific outputs like crypto filing deltas and classification summaries. It distinguishes from siblings by directing users to readiness for service health and issuer-specific tools for detailed research.

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