List Checklist Schedule Attachments

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

Annotations already indicate read-only and idempotent behavior. The description adds that the tool returns paginated JSON arrays with pagination metadata, which is useful context beyond the annotations. No contradictions are present.

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 two sentences plus an API reference line. It is fairly concise, though the first two sentences partially repeat the tool's purpose. The API line provides extra but useful context. Not overly verbose.

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?

There is no output schema, so the description must explain what is returned. However, it states 'Returns a paginated JSON array of Inspections,' which conflicts with the tool name and title indicating 'Attachments.' This inconsistency undermines completeness. Additionally, the description does not specify the structure of the response items.

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 description coverage is 100%, so each parameter already has a clear description. The tool description adds that project_id and schedule_id are required and mentions pagination parameters, but this is largely redundant with the schema. 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 verb (list) and resource (checklist schedule attachments), but it also says 'enumerate Inspections' which misidentifies the returned resource as inspections rather than attachments. This inconsistency reduces clarity despite an otherwise clear statement of purpose.

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 explains when to use the tool ('when you need a paginated overview, to find IDs, or to filter by query parameters') and mentions required parameters. However, it does not explicitly state when not to use it or suggest alternative tools, though the specificity provides sufficient guidance.

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