recall_tool_runs

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

Declares read-only and bounded summaries, consistent with annotations. Adds details on limits and payload condition. No contradiction with annotations.

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, front-loaded with purpose, includes key usage details. Slightly dense but acceptable.

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?

Covers filtering, limits, payload inclusion, and return structure. Output schema handles return values. Lacks pagination details but adequate for a read-only recall 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?

Schema coverage is 0% and description covers 6 of 9 parameters (toolName, outcome, requestId, since, until, limit, includePayload). Misses projectId and projectRef. Partially compensates but not fully.

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 'inspect prior project tool_runs' with specific filtering criteria. Distinguishes from sibling tools like 'recall_answers' by focusing on tool runs.

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 default limit, max limit, and payload inclusion detail. Implicitly suggests using requestId for agent_feedback. Does not explicitly contrast with alternatives, but usage context is clear.

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