List Punch Item Trade Filter Options

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

Annotations already indicate readOnly and idempotent. Description adds pagination and search capabilities, as well as the endpoint URL. No contradictions. With annotations present, this is adequate but not rich.

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 covering action, usage, return type, and API reference. Front-loaded with the main purpose. Could be slightly tighter but no extraneous content.

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?

For a filter options list endpoint with good schema and annotations, description is mostly complete. Lacks details on search behavior or error cases, but not critical for this type of 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%, so the schema fully documents parameters. Description mentions required params (already in schema) and hints at pagination/search but adds no new semantic meaning beyond schema descriptions.

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 states it returns trades associated with punch items with pagination and search. However, it misleadingly says 'enumerate Punch List records' when it actually returns filter values, not records. Slightly ambiguous but still clear enough to distinguish from siblings.

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 context for use ('when you need a paginated overview, to find IDs, or to filter by query parameters') but doesn't specify when not to use it or alternatives. Sibling tools are similar but name distinguishes them; no explicit guidance against using this for other filter options.

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