patternfetch_delta

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

With no annotations, description discloses key behaviors: returns changed=false when nothing changed, provides impersonal data not advice, and focuses on minimal tokens. Implies statefulness (requires previous brief) without fully detailing prerequisites or rate limits.

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 plus a WHEN clause; front-loaded with purpose, efficient with no fluff. Every sentence adds value: what, when, result on no change, disclaimer.

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?

Adequate for a delta tool: explains purpose, usage, return flag, and uses sibling names for context. Could be more explicit about state dependency and output format, but given 3 param inputs and no output schema, it covers essential aspects.

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 description must compensate. It explains ticker and timeframe as 'ticker+timeframe' but omits the optional 'limit' parameter. Adds meaning to required params but not complete 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?

Description clearly states verb 'Get only what CHANGED' and resource 'since your last brief for a ticker+timeframe', listing specific change types like trend flips and RSI-state changes. It distinguishes from sibling tools (e.g., patternfetch_brief, patternfetch_analogs) by focusing on delta updates.

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: 'when an agent polls the same market repeatedly and wants minimal tokens'. Implies not for first-time queries, and sibling names provide context for alternatives, but no explicit exclusions.

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