List Checklist List Trade Filter Options

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

Annotations already indicate readOnly and idempotent. The description adds that it is a GET endpoint with pagination and search, and that it returns a JSON array. However, it does not disclose potential error conditions or the exact structure of the returned array beyond basic filter values.

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 four sentences but contains redundancy and a contradictory phrase ('enumerate Inspections' vs 'trades'). It could be more concise and focused without the confusing element.

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 annotations, the description covers the basic functionality. However, it lacks details about the response item structure (e.g., id, name) and does not mention error handling or default values for pagination.

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 input schema has 100% description coverage, so the baseline is 3. The description mentions 'pagination and optional search', which aligns with page, per_page, and query parameters, but it does not add significant meaning beyond the schema's own 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?

The description states it returns trades, but then says 'Use this to enumerate Inspections' which is contradictory and confusing. The core purpose of listing trade filter options is not clearly conveyed, and the mention of 'Inspections' misleads about the resource being returned.

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 provides some guidance on when to use the tool (for paginated overview, finding IDs, filtering by query), but it does not explicitly distinguish this tool from other similar filter option tools or state when not to use it.

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