feedbin_list_saved_searches

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, yet it only implies a read-only enumeration via the word "List." It says nothing about authentication requirements, whether results are paginated, what a saved search object contains, or the ordering of results.

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?

A single three-word sentence, front-loaded and free of padding, which is appropriately sized for a zero-argument list operation. The terseness is under-specification rather than verbosity, so it isn't penalized here.

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?

For a trivial zero-parameter, read-only list tool with no output schema, the description is minimally sufficient to call it correctly. However, with no output schema the agent has no idea what fields a saved search record returns (query string? name? id?), which would matter for any follow-up call.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; the absence of parameters is itself the relevant semantic fact and the description is consistent with it.

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?

"List saved searches" is a verbatim restatement of the tool name feedbin_list_saved_searches and adds no information an agent doesn't already have. It does not distinguish this from siblings like feedbin_get_saved_search or feedbin_create_saved_search, so the agent must infer the boundary from naming conventions alone.

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?

There is no guidance on when to use this versus feedbin_get_saved_search (single lookup) or the create/update/delete saved-search siblings. The agent is left to infer that "list" means enumeration, with no stated preconditions or exclusions.

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