List Permission Templates

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

Adds substantial behavior beyond the annotations: pagination behavior ('page and per_page control pagination and the response reports how many pages remain'), error semantics (401/403/404), and the company_id default from procore_set_config. The read-only note aligns with annotations without contradicting them.

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 a single, well-organized paragraph where every sentence adds value: purpose, use case, default, pagination, read-only nature, errors, required parameters, and API endpoint. No filler or redundancy.

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?

Despite no output schema, the description covers the essential runtime context: return shape (JSON array of permission templates), pagination, error conditions with status codes, and required parameters. For a moderate-complexity list tool, this is thorough and sufficient for an agent to invoke it correctly.

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 baseline is 3. The description adds value beyond schema by explaining the company_id default ('defaults to the value set by procore_set_config when omitted') and clarifying that page/per_page control pagination, which goes beyond the schema's field 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 it returns permission template names and IDs for a specified company, with a specific use case: 'discover permission templates or to look up the id of one before calling a tool that needs it.' This verb+resource+scope specification distinguishes it from siblings like the project-level or user-specific template list 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?

Provides explicit usage context ('Use this to discover permission templates or to look up the id...'), but does not mention when not to use it or name alternative tools. It gives clear when-to-use guidance without exclusions, earning a 4 rather than a 5.

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