feedbin_create_saved_search

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

With no annotations, the description carries the full behavioral burden. "Mutates Feedbin state" is better than nothing, but it restates what "create" already implies and reveals nothing about validation of the query, whether duplicates are allowed, whether the response returns the new ID, or error/permission behavior.

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?

Two short sentences with zero filler and the purpose front-loaded. The size is appropriate for the dimension, though the second sentence adds little information.

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?

A write operation with zero annotations, no output schema, and two entirely undocumented parameters. The description should at minimum explain the query parameter's format and whether the created resource is returned; it does neither.

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 0% and both required parameters (name, query) are completely undocumented. The description does not explain what "name" means (a label?), nor does it give any hint about the query syntax, which is critical for a search tool.

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?

States a specific verb+resource ("Create a saved search") that an agent can distinguish from list/get/update/delete saved search siblings. It does not explicitly name the siblings or scope the operation further, but the core purpose is unambiguous.

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?

No guidance on when to create a saved search versus using a query directly, no prerequisites, and no mention of the read-oriented siblings. The agent is left to infer usage entirely from the name.

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