List Configurable Field Set Project Options

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

Annotations already cover safety (readOnly, idempotent). Description adds that it returns a paginated JSON array with pagination metadata, and includes endpoint reference. Does not address openWorldHint, but overall adds useful context.

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?

Four sentences: purpose, use cases, return description with pagination, required params and API reference. Front-loaded, no wasted words.

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?

Comprehensive for a list tool with robust annotations and full schema coverage. Explains return value (paginated JSON array with metadata) and required params. No gaps.

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%, baseline 3. Description groups parameters into pagination (page, per_page) and filtering (with_name, starts_with), and highlights required ones, adding meaning beyond 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?

Clearly states it returns projects for a configurable field set, using specific verb and resource. Distinguishes from sibling list tools like list_configurable_field_sets which list field sets themselves.

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 usage contexts: enumerating Custom - Configurable Tools for paginated overview, finding IDs, or filtering. Does not explicitly exclude alternatives but sufficiently clarifies when to use.

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