Show Checklist (Deprecated)

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

The annotations already declare readOnlyHint/idempotentHint/destructiveHint, and the description adds value by explicitly stating 'Read-only — it changes nothing' and detailing failure modes with common HTTP statuses (401, 403, 404). Deprecation notice also adds behavioral context beyond the 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 detailed but well-organized: purpose first, then deprecation, usage, return type, errors, required params, and API reference. All sentences contribute, though the 'Read-only' phrase is redundant with annotations. Slightly verbose but not wasteful.

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 no output schema, the description covers return type ('single JSON object'), error behavior, deprecation, usage prerequisites, and required parameters. For a simple GET-by-ID tool with strong annotations, this is highly complete.

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 both id and project_id. The description only restates they are required, which is already in the schema. It adds no new meaning beyond the schema, so baseline of 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 starts with 'Retrieves Inspection Checklist in a specified Project,' which clearly states the verb and resource. It further distinguishes this tool by noting it returns the full field set for a known checklist, separating it from sibling list/search tools.

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?

It explicitly says 'Use this when you already know which checklist you want' and instructs to resolve the id with a list tool first. It also directs users to procore_search_endpoints for a newer version due to deprecation, providing clear when-to-use and alternative guidance.

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