get_filters

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

No annotations, but the description covers return format (JSON array with id, name, type), the effect of the optional filter_type parameter, and that it retrieves all filters if unspecified. No destructive behavior mentioned, consistent with a read operation.

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?

Well-structured with Args, Returns, and Examples sections. Every sentence adds value, no fluff.

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?

Comprehensive for a simple list tool with one parameter. Explains return format, usage pattern, and integration with other tools. Output schema exists but description still clarifies content.

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 0%, but the description fully documents the single parameter filter_type: lists valid values (deals, persons, etc.) and explains default behavior. Adds meaning beyond the schema.

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 tool retrieves saved filters from Pipedrive, explaining their use with other tools like get_deals. It distinguishes from siblings by focusing on filter retrieval, which is unique among the listed tools.

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?

Provides explicit when to use: to get filter IDs for custom field queries, with a step-by-step process. Lacks explicit when not to use, but the context is sufficient for correct selection.

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