List Available RFI RFI Manager Filter Options

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds that it returns a JSON array of available filter values for RFI records, specifies required parameter project_id, and gives the full API endpoint. This adds useful context beyond annotations without contradiction.

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 three sentences, covering purpose, usage, and endpoint. It is concise and front-loaded with key information, though it could be slightly more streamlined.

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 simple filter listing tool with no output schema, the description adequately explains what it returns and how to use it. It includes the endpoint and required parameter. The pagination parameters are covered by the schema. It is complete enough for its complexity.

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 descriptions for project_id, page, per_page. The description mentions required parameters but does not add significant meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 available RFI Manager filter fields and options for RFIs on a specified project. It also specifies the use case: to enumerate RFI records for paginated overview, find IDs, or filter by query parameters. This differentiates it from sibling tools like list_available_rfi_assigned_id_filter_options, as it is specifically for the RFI Manager filter.

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 provides explicit use cases: 'Use this to enumerate RFI records when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not explicitly state when not to use or mention alternatives, but the context of sibling tools makes it clear this is for the specific RFI Manager filter.

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