list_saved_searches

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which the description does not contradict. The description adds 'all' to indicate the scope (no filtering), providing some context beyond annotations, but it does not disclose other behavioral aspects like pagination or ordering.

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 minimal and directly front-loads the main purpose. It includes a clear 'Args' section for the parameter, with no redundant information. Every sentence earns its place.

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?

Given there is an output schema and the annotations cover the safety profile, the description is adequate for calling the tool. However, it lacks usage context (when to use vs alternatives) and does not mention any edge cases or additional behaviors. It is sufficient but not rich.

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 schema has one parameter 'instance' with only a title and default, giving no semantic meaning. The description partially compensates by stating 'instance: YouTrack instance (optional)', which clarifies its purpose and optionality. However, it does not specify format or examples, leaving some ambiguity.

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 function as 'List all saved searches (queries)' with a specific verb 'List' and resource 'saved searches'. This distinguishes it from sibling tools like run_saved_search, which executes a search rather than listing them.

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. It does not mention run_saved_search or any other related tool, nor any conditions or exclusions. Agents must infer usage solely from the name.

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