List Project Vendor Insurances

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, providing a safety profile. The description adds value by noting pagination behavior with page/per_page and that response includes pagination metadata. No contradictions with 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 4 sentences and front-loads the main purpose. It includes key usage notes and pagination details. Could be slightly more concise (e.g., 'Returns paginated insurances for a project vendor; use page/per_page for pagination'), but overall efficient.

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?

No output schema is provided, so the description should compensate by describing the returned data structure. It mentions 'paginated JSON array of Directory records' and pagination metadata but does not specify the fields of insurance objects. For a list tool with 5 parameters, this is adequate but incomplete.

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 for all 5 parameters, so the schema itself documents them well. The description mentions page/per_page for pagination and required parameters but does not add extra semantic meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 returns a list of insurances for a specified project vendor. It mentions pagination and filtering, making the purpose specific. However, it does not differentiate from sibling tools like 'list_company_vendor_insurances' or 'sync_project_vendor_insurances', which reduces clarity slightly.

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 tells when to use the tool (enumerate directory records, find IDs, filter) and lists required parameters. However, it does not specify when NOT to use it or mention alternatives (e.g., using sync or company-level lists). This leaves gaps for an agent deciding between tools.

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