SimpleFunctions

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

With no annotations provided, the description carries the full burden. It successfully discloses 'Read-only' status and 'no rate limit.' It also details what data structures are returned in each mode (causal tree, signal log, evaluation history for thesis; price movers, highlights for global). Minor gap: doesn't mention error handling or caching behavior.

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

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

Excellent front-loading with 'START HERE' priority signal. Logical flow: purpose → global mode specifics → thesis mode specifics → behavioral traits → usage guidelines. Every sentence conveys unique information with zero 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 no output schema and no annotations, the description comprehensively compensates by detailing return contents for both modes (mispriced edges, causal trees, signal logs, etc.). It covers auth requirements, rate limits, and sibling relationships. Complete for a multi-mode entry-point 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?

While schema has 100% description coverage (baseline 3), the description adds crucial semantic context: it explains that thesisId requires apiKey when set, describes the 'global mode' vs 'thesis mode' concept, and clarifies that apiKey is ignored in global mode. This elevates it above 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 explicitly states the dual purpose: returning 'either a global market snapshot or a thesis-specific context bundle.' It clearly delineates the two modes (global vs. thesis) and distinguishes from siblings by explicitly naming get_edges, get_changes, and get_world_state as alternatives for single slices.

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?

Provides explicit workflow guidance ('START HERE', 'Use this first') and clear exclusion criteria ('only call get_edges... if you need that single slice in isolation'). It clearly maps parameter combinations to modes (no args = global, thesisId + apiKey = thesis-specific).

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