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

With no annotations, the description carries the full burden and does well: it discloses per-call pricing ($0.005), the two payment paths (x402/USDC on Base vs. subscriber API key via three header/query forms), the opinion-vs-fact labeling on our_opinion, and an educational-not-advice disclaimer. It omits rate limits and any explicit read-only confirmation, keeping it from a 5.

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

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

Front-loads price and purpose, then layers in returns, disclaimer, and payment mechanics. The HOW TO PAY block is verbose but earns its place for a paid API with no annotations. Slightly long overall but well ordered.

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?

Covers the return contents, pricing, payment, and legal posture despite having no annotations or output schema. An agent can call it correctly. A tighter statement of response shape and the limit/symbol semantics would make it fully complete.

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

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

Schema coverage is 0%, so the description must compensate. It establishes that symbol is an optional filter and that results cap at 25 ideas, which adds meaning. But it never explains the limit parameter's default (10) or its maximum relationship to the 25-idea cap.

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

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

States a concrete verb+resource: it returns the most recent cross-agent market-intelligence ideas (institutional flow, options flow, on-chain, news catalysts) from a 40-source SharedBrain, plus top primary_scoops and spaces. This is specific and content-rich. It does not explicitly name which sibling to prefer (e.g., get_signals, get_narratives), so it stops short of 5-tier differentiation.

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?

Gives operative context — optional symbol filter, up to 25 ideas per call, and that get_catalog should be browsed first for pricing. However, it never states when to choose this aggregator over siblings like get_signals, get_primary_scoops, or get_narratives, so alternative selection is left to inference.

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