List Filter Options For For Record Only

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which inform the agent that the tool is safe and idempotent. The description adds that it returns a JSON array and includes the endpoint path, but does not provide substantial behavioral details beyond the annotations. No 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 fairly concise, consisting of a few sentences that cover purpose, usage, return type, required parameters, and API reference. It is front-loaded with the main action. However, it includes some redundant info (e.g., endpoint path could be considered implicit) but overall well-structured.

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?

The description explains the return type (JSON array of filter values) and lists required parameters, which is adequate for a list tool. However, it lacks details on the structure of individual filter values, which would be helpful since no output schema is provided. For a tool with 3 well-documented parameters, it meets minimum completeness but could improve.

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 description coverage is 100%, with clear descriptions for project_id, page, and per_page. The description only reiterates 'Required parameters: project_id' and mentions pagination in usage. It adds no new meaning or context beyond the schema, so 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 the verb 'Returns' and the resource 'Filter Options for For Record Only' for submittals. It mentions enumerating submittals and pagination. However, it does not explicitly differentiate from other filter option tools among the many sibling tools, though the name is 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 provides use cases (paginated overview, find IDs, filter by query parameters) and mentions the required parameter. However, it does not offer guidance on when not to use this tool or point to alternatives, which is a gap given the large number of sibling filter option tools.

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