List Image Categories

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral details: it returns a paginated JSON array, pagination is controlled by page and per_page, and the response includes pagination metadata. No contradictions with 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 four sentences, front-loaded with the main purpose. Each sentence adds value: primary action, usage context, pagination details, and endpoint reference. No unnecessary information.

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?

For a list endpoint with three fully documented parameters and no output schema, the description provides essential context: the endpoint type (GET), pagination behavior, and the Procore API category. It covers the necessary information for correct invocation, though a bit more detail on response structure could be beneficial.

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 clear parameter descriptions. The description adds value by explicitly stating that project_id is required and clarifying that page/per_page control pagination with metadata in the response. It reinforces the schema and adds context about pagination behavior.

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 a list of all Photo Albums (Image Categories) in a specified project. It also describes the use case for enumeration, finding IDs, and filtering. The verb 'Return a list' combined with the resource makes the purpose highly specific.

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 explicitly states when to use the tool: 'Use this to enumerate Photos when you need a paginated overview, to find IDs, or to filter by query parameters.' However, it does not explicitly mention when not to use it or provide direct comparisons with sibling tools from the extensive list.

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