List Punch List Assignee Options

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

The description adds behavioral context beyond annotations: it specifies pagination ('paginated JSON array'), metadata, and the required endpoint. It does not contradict annotations (readOnlyHint, etc.). However, it omits details like rate limits or auth specifics.

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 three sentences and front-loads the purpose. It is reasonably concise, though the final sentence listing the Procore API and endpoint is verbose for context signals.

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?

Given no output schema, the description mentions 'paginated JSON array' and pagination metadata, which is moderately helpful. However, it lacks details on the fields returned or the structure of the pagination metadata.

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%, so the description adds little beyond schema. It repeats that project_id is required and mentions pagination control, but does not provide new meaning.

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 it returns login information assignable to Punch Items, and explicitly says to use it for enumerating punch list records with pagination and filtering. It differentiates itself from sibling tools by focusing on assignee options.

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 clear usage context: 'enumerate Punch List records when you need a paginated overview, to find IDs, or to filter by query parameters.' It mentions required parameters and pagination control, but does not explicitly state when not to use it or compare to alternatives.

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