List Lien Waivers

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds that it returns a paginated JSON array with metadata, which is useful but not extensive. No additional behavioral traits like rate limits or auth requirements are mentioned, so the description adds moderate value beyond 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?

The description is about 5 sentences and front-loaded with the tool name. However, it includes redundant and contradictory phrasing (invoices vs lien waivers) which adds unnecessary length and confusion. It could be more concise and accurate.

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 list tool with 4 parameters and no output schema, the description covers pagination and required params fairly well. However, the critical inaccuracy about returning invoices instead of lien waivers leaves a gap in completeness, as it misrepresents the tool's output.

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 baseline is 3. The description explains the purpose of page and per_page parameters for pagination and includes the endpoint path clarifying project_id as a path parameter. This adds meaningful context beyond the 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?

The description clearly states 'List Lien Waivers' as the main purpose, but then contradicts itself by saying 'enumerate Invoices' and 'Returns a paginated JSON array of Invoices.' This inconsistency muddles the purpose and may mislead an agent into thinking the tool returns invoices rather than lien waivers.

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 usage scenarios like 'paginated overview, find IDs, filter by query parameters' but does not differentiate from sibling tools like list_invoices or specify when not to use this tool. The guidance is implied but lacks explicit alternatives or exclusions.

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