get-raw-data

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

Discloses the 300-record limit and truncation message. No annotations provided, so description carries full burden; it effectively conveys read-only behavior without side effects.

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 with no redundancy: first states core function, second adds limit and guidance. Every sentence earns its place.

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?

Adequately covers input and behavior given the tool's simplicity and lack of output schema. Could mention return format, but limit detail compensates.

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 already describes hash_id fully; description adds value by directing users to the 'recent-queries' resource for valid IDs, enhancing parameter usability.

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 action (retrieve), resource (raw data from cache), and key identifier (hash ID). Distinguishes from sibling 'export-raw-data' which is about exporting.

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 hint to use 'recent-queries' resource for hash IDs, but does not explicitly state when to use this tool versus alternatives like export-raw-data.

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