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

With no annotations, the description carries the full burden. It discloses the cost ($0.5), payment methods (x402 or API key), data composition (pure derived reads, no raw vendor data), educational disclaimer, and authentication options. While it does not explicitly state that it's a read-only operation, the nature of a tearsheet implies it, and the payment details add useful context beyond the schema.

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 moderately long but front-loaded with the core purpose, followed by data source, disclaimer, payment methods, and a catalog pointer. Each sentence adds value: cost, contents, composition, disclaimer, payment, and catalog recommendation. There is no redundant filler, though the payment details make it slightly verbose.

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

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

For a tool with one parameter, no output schema, and no annotations, the description provides enough context for a user to understand its purpose, inputs, cost, and authentication. It lists the data components (market regime, composite signal, social sentiment, institutional moves), giving a clear idea of what the response includes. It could be more explicit about the response format, but the listed components suffice for retrieval.

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

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

The schema has only one parameter 'symbol' with no additional description (0% coverage). The tool description adds meaning by clarifying that the symbol is a ticker: 'for one ticker', 'per-symbol', and 'one-call per-symbol tearsheet'. This compensates for the schema's lack of detail, though it doesn't specify format constraints (e.g., uppercase, exchange suffixes).

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: 'one-call per-symbol tearsheet' that combines market regime, composite signal conviction, social sentiment, and 13F moves for a single ticker. This specific verb+resource structure distinguishes it from sibling tools like get_symbol_sentiment or get_market_regime, which target individual data points.

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 a consolidated view ('one-call') but does not explicitly state when to use this tool versus individual tools like get_symbol_sentiment or get_market_regime. It mentions browsing the catalog but gives no clear guidance on selection criteria or when not to use it. The guidance is implicit rather than explicit.

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