get_daily_market_wrap

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

No annotations provided, so the description carries the full burden. It discloses that the tool returns a broad range of data including an AI-generated narrative summary. It implies read-only behavior (no mutations). Could mention rate limits or auth, but for a data retrieval tool, the description is sufficiently transparent.

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: first specifies purpose and contents, second gives usage context. No redundancy, front-loaded with key information. Every sentence is necessary and well-placed.

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

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

No output schema, so description explains return values comprehensively (price moves, breadth, announcements, insider trades, dividends, board changes, narrative summary). Covers daily and weekly contexts. Adequate 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%. The parameter 'days' has a description in the schema. The description adds extra guidance: 'Use 1 for last trading day.' This adds value beyond the schema, meriting a score above baseline 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?

Clearly states the verb 'Get' and resource 'daily NZX market wrap'. Describes specific contents (price moves, breadth, etc.) and explicitly distinguishes from siblings by being a comprehensive digest, unlike sibling tools that focus on individual aspects.

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 usage guidance: 'Use for questions about today's NZX market, overall market conditions, what happened across the NZX, or weekly market summary.' This clarifies when to use this tool over more specific sibling tools.

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