global_recall

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

Declares read-only nature and no side effects. Discloses return limit of 50 and partial match behavior. Could mention error handling for invalid instance_id 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?

Four sentences, well-structured with key information front-loaded. Efficient but covers all needed aspects without 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?

Covers purpose, usage, behavioral aspects, and parameter semantics adequately. Lacks mention of possible return formats or empty result behavior, but sufficient for a simple retrieval 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 100%. Description adds meaning for topic (optional, partial match, returns all if omitted) but adds little to instance_id beyond what schema says.

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 it retrieves cross-project lessons stored via global_learn. Specifies it is read-only and distinguishes from siblings by naming alternative tools for different scopes.

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 describes when to use (cross-project lessons) and when to use alternatives (recall_best_solution for project-specific, team_recall for org-scoped). Provides guidance on topic filtering.

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