history

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

Discloses it reads from local profile store and does not re-profile the warehouse, indicating a non-destructive read operation, but lacks details on capping behavior, authorization, or data freshness.

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 concise sentences: first states purpose, second adds behavioral context. Every word is necessary with no 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?

With only one simple parameter and an output schema present, the description covers the core idea but omits specifics about the cap, anomaly types, or result structure, leaving gaps for a complete understanding.

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?

Adds meaning by explaining the 'days' parameter specifies the time window, but does not elaborate on allowed values, range, or cap limit beyond what the schema indicates (default 30).

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 specifies the tool returns anomalies within a time range, using a specific verb ('Return') and resource ('anomalies recorded'), and distinguishes from siblings like 'check' and 'investigate' by focusing on historical data with a time constraint.

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?

Implies usage for quick reads from local profile store without warehouse re-profiling, but no explicit when-to-use or contrast with siblings like 'investigate' which may also deal with anomalies.

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