get_completed_picks

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

No annotations are provided, so the description carries the full burden. It accurately describes a read-only operation returning completed picks with results, which is transparent. However, it could be more explicit about ordering or time range (e.g., 'recently' is vague).

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?

The description is extremely concise with two sentences plus a structured Args/Returns section. Every sentence adds value without extraneous information.

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?

Given the tool's simplicity and the presence of an output schema (not shown), the description provides sufficient context: it lists the output as 'List of completed picks with results (W/L) and details'. This is adequate for understanding the return value without being overly detailed.

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?

The description adds significant meaning beyond the input schema: it explains the limit parameter's purpose (number of recent completed picks), default (20), and maximum (50). The schema only shows type and default, so the description provides essential constraints and context.

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?

The description clearly states the tool gets 'recently completed (resolved) picks with results', which distinguishes it from siblings like get_pending_picks (unresolved) and get_todays_picks (today's picks, potentially not completed).

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?

The description implies usage for recently completed picks but does not explicitly provide when-to-use or when-not-to-use guidance compared to alternatives. The context from sibling names helps, but no direct exclusions are given.

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