List Checklist List Point Of Contact Filter Options

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that the tool returns a JSON array, uses pagination, and requires specific parameters. It does not disclose behavior on empty results, error handling, or rate limits beyond what annotations imply.

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 concise with two main sentences plus endpoint info. It front-loads the core action and purpose. No extraneous text, though minor repetition of 'Inspections' could be tightened.

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?

With 7 parameters and no output schema, the description should explain response structure more. It states 'JSON array of available filter values' but not the fields inside. It also does not mention the 'view' parameter's effect (recycle bin), though present in schema. Basic completeness for a simple list endpoint.

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?

Input schema has 100% coverage, so baseline is 3. Description only repeats required parameters and mentions pagination/search, but adds no additional meaning for parameters like page, per_page, query, filters, or view 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 the tool returns points of contact for inspections with pagination and optional search. It distinguishes itself from sibling filter option tools by specifying it returns point of contact filter values, not other filter types.

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 a use case: 'Use this to enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters.' However, this is somewhat misleading as the tool returns filter options, not inspections. It does not explicitly mention when not to use or compare to alternatives among many sibling filter tools.

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