List Custom Field Sections

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds valuable context beyond that: it details pagination behavior ('response reports how many pages remain'), error payloads with common HTTP status codes, and confirms 'Read-only — it changes nothing in Procore.' This adds meaningful behavioral disclosure.

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?

Every sentence earns its place: purpose, use case, return format, pagination, read-only guarantee, error handling, required parameter, and API reference. It's front-loaded with the primary action and efficiently packed without 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?

With no output schema, the description provides enough context: it returns a JSON array, explains pagination, mentions error formats, and states the required parameter. It stops short of detailing the array's internal structure, but that's not essential for tool selection and invocation.

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 descriptions for all three parameters. The description only reinforces that page/per_page control pagination and calls out company_id as required, adding minimal extra meaning beyond the schema.

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 opens with a specific verb and resource: 'Return a list of all Custom Field Sections associated with the Current Company.' It clearly differentiates from sibling tools like list_configurable_field_set_sections by targeting a distinct resource and explains the purpose of discovering sections or looking up ids.

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 states when to use the tool: 'Use this to discover custom field sections or to look up the id of one before calling a tool that needs it.' This gives clear context for usage, though it doesn't name specific alternatives or exclusions, which would merit a 5.

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