get_query_parameters

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

No annotations are provided, so the description carries the full burden. It mentions 'May require special permissions,' which adds useful context about potential authentication needs. However, it lacks details on rate limits, return format, or other behavioral traits, making it only partially transparent.

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 brief and front-loaded with the main purpose, followed by a note. It avoids unnecessary words, but could be slightly more structured (e.g., separating the note). Overall, it's efficient but not perfectly optimized.

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 1 parameter with 0% schema coverage and an output schema exists, the description is incomplete. It doesn't explain the parameter or return values, though the output schema mitigates some gaps. For a tool with no annotations and low schema coverage, it should provide more context to be fully helpful.

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%, so the description must compensate. It doesn't explain the 'site_url' parameter beyond what the schema provides (just a string). No additional meaning, format requirements, or examples are given, failing to address the coverage gap.

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 states the tool 'Get URL normalization parameters' which indicates it retrieves parameters for URL normalization. However, it's somewhat vague about what 'URL normalization parameters' specifically are and doesn't distinguish this from sibling tools like 'get_query_stats' or 'get_query_page_stats' which might have overlapping domains.

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 includes a note about special permissions, which provides some context, but doesn't explicitly state when to use this tool versus alternatives. There's no guidance on scenarios where this tool is preferred over similar siblings like 'get_query_parameter' or 'get_query_stats', leaving usage unclear.

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