List Potential Points Of Contact

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds value by explaining pagination (page, per_page), returned paginated JSON with metadata, and the API endpoint. 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 four sentences: purpose, usage, output, pagination control, required params, and API info. It is front-loaded and avoids fluff, though some repetition exists (e.g., 'paginated JSON array' and 'pagination metadata').

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, annotations, and no output schema, the description covers pagination and required params. However, it does not explain the nature of 'potential points of contact' or the response object structure, leaving some gaps.

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% with descriptions for all 4 parameters. The description mentions page and per_page for pagination and project_id as required, but adds little beyond the schema. The phrase 'filter by query parameters' applies to vendor_id, but schema already covers it. 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 lists Potential Points of Contact in a specified Project. It mentions enumeration of Inspections, which may cause slight confusion as the tool is about contacts, not inspections themselves. The purpose is distinct from sibling tools like list_checklist_list_point_of_contact_filter_options, but could be more precise.

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 context: enumerating Inspections, pagination, finding IDs, filtering. It indicates required parameters. However, it does not explicitly state when not to use or offer alternatives, which would improve guidance.

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