List Filter Options For Private

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 endpoint and API reference details, which are useful but do not significantly expand on behavioral traits beyond what annotations convey. No contradictions.

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 concise, with two sentences plus additional context. It front-loads the core purpose. The mention of 'enumerate Submittals' slightly detracts but overall is efficient.

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 the simple nature of a filter options list tool, the description adequately covers purpose, usage, and required parameters. It notes the return format (JSON array) and references the Procore API. No output schema, so the description compensates sufficiently.

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%, and the description does not add any parameter-specific information beyond the schema. It mentions required parameters and the endpoint but does not explain how page/per_page affect results or provide additional context.

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 that the tool returns all Filter Options for Private for the project. It specifies the resource (filter options) and the context (private submittals). Sibling tools exist for other filter options, so 'Private' distinguishes it, but the description could be more explicit about that differentiation.

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 advises using this to 'enumerate Submittals' when needing paginated overview, IDs, or filtering. However, the tool returns filter options, not submittals themselves, which is somewhat misleading. It does not provide clear when-not-to-use or alternative tools.

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