List Filter Options For Created By

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it returns a JSON array of filter values, providing some return format context. It does not disclose pagination behavior or rate limits, but with annotations covering safety, the description adds marginal value.

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 four sentences long, containing some redundant information like the API section and full endpoint URL, which may not be essential for an AI agent. It could be more concise while retaining key points.

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 states it returns 'a JSON array of available filter values for Submittals', but lacks detail on the structure of each filter option (e.g., id, label). It adequately covers the basic purpose but could be more complete about output specifics.

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 all three parameters (project_id, page, per_page). The description only repeats that project_id is required, adding no further semantic value. Baseline 3 is appropriate as the schema already does the heavy lifting.

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 all Filter Options for Created By for the project, specifying the resource and action. However, it slightly confuses by saying 'enumerate Submittals' whereas this endpoint lists filter options, not submittals themselves. It distinguishes from siblings by naming the specific 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 suggests using this to enumerate Submittals for pagination or filtering, which is misleading since this tool only returns filter option values. It does not provide guidance on when to use this versus other filter options or alternative tools like list_submittals. No explicit when-not or alternative references.

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