list_saved_searches

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic operation without detailing authentication needs, rate limits, or scope of 'all.' The agent cannot infer whether this lists global, user-specific, or instance-specific searches.

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 extremely concise: one sentence for purpose and one line for the parameter. Every word adds value, with no redundancy or filler. This is appropriately sized for a simple tool with a single optional parameter.

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?

Despite having an output schema that may explain return values, the description lacks details about pagination, sorting, or fields returned. It is minimally complete for a list operation but omits common considerations like result limits or filtering.

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 input schema has 0% description coverage, leaving the parameter 'instance' undocumented. The description adds 'YouTrack instance (optional),' which clarifies its purpose and optionality. However, it does not specify the expected format (e.g., URL or ID), so the value is moderate.

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 action: 'List all saved searches (queries).' The verb 'list' and resource 'saved searches' are specific. While it does not explicitly differentiate from sibling tools like 'run_saved_search', the action is distinct enough for an agent to understand its purpose.

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 no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it. For example, it does not clarify if this should be used before 'run_saved_search' or if it replaces other list operations.

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