List Filters

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

Annotations indicate readOnly and idempotent, which aligns with a list operation. However, the description contradicts itself by claiming to list filters but returning portfolio records, misleading about the output. Pagination behavior is explained, but the core output mismatch undermines transparency.

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 short but includes redundancy (e.g., 'paginated' mentioned twice) and a confusing shift from 'list filters' to 'enumerate Portfolio records.' It front-loads the purpose but could be more streamlined and consistent.

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?

With no output schema, the description should fully explain the return value. It only vaguely mentions 'paginated JSON array of Portfolio records' and 'pagination metadata,' leaving the actual structure and the nature of 'filters' unexplained. The inconsistency further reduces completeness.

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%, so parameters are already documented. The description reiterates required parameters and explains page and per_page usage for pagination, adding minimal extra meaning beyond the schema. 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 states 'List all filters' but then says 'Returns a paginated JSON array of Portfolio records,' creating ambiguity about whether the tool returns filters or filtered records. The verb and resource are not consistently aligned, making the purpose unclear.

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 usage context: 'Use this to enumerate Portfolio records when you need a paginated overview, to find IDs, or to filter by query parameters.' It mentions the endpoint and required parameters, but does not explicitly state when not to use the tool or differentiate from siblings like list_filters_company.

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