List Custom Field Sections

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

Annotations already declare readOnlyHint, idempotentHint, so the safety profile is known. The description adds value by noting pagination behavior (page, per_page, metadata) and the endpoint path, providing useful context beyond 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 front-loaded with the main purpose and includes necessary details like pagination and required parameters. It is concise but could be slightly trimmed (e.g., the endpoint URL is extra but not harmful).

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 adequately explains return value (paginated JSON array) and mentions pagination metadata. It covers the key aspects needed for an agent to use the tool 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%, but the description adds guidance on pagination usage ('Use page and per_page to control pagination; the response includes pagination metadata') and highlights the required company_id, enhancing understanding 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 clearly states the tool returns a list of all Custom Field Sections for the Current Company, using specific verb 'Return a list'. It also enumerates use cases (paginated overview, find IDs, filter by query parameters), making the purpose unambiguous.

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 advises when to use the tool, i.e., 'Use this to enumerate Custom - Configurable Tools when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not provide negative examples or alternatives, but the context is clear.

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