getQueries

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

With no annotations, the description must disclose behavior but only says 'List queries'. It does not mention that the tool supports format selection (json/xml) via pathParams, pagination via queryParams, or that it returns a list of query objects. The agent is left to infer behavior from the schema.

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 (two words) but fails to add value beyond the tool name. It does not front-load key information like what 'queries' are or that pagination is available. The brevity sacrifices necessary detail.

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?

The tool has no output schema, no annotations, and a complex nested input schema. The description is far too minimal to be contextually complete. It does not describe the return format, pagination behavior, or how the format parameter affects output.

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% (meaning no param descriptions in schema), and the tool description provides no additional meaning for any parameter. The existence of required pathParams and queryParams is not explained, leaving the agent without guidance on how to use them.

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?

Description 'List queries' is a tautology with the tool name 'getQueries' and provides no clarification on what 'queries' refers to (e.g., saved search queries vs. database queries). It does not distinguish from sibling tools like getIssues or getProjects.

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 use this tool versus alternatives. For example, it does not specify if this lists all queries or only those accessible to the user, nor does it mention pagination or filtering options that might affect usage.

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