add_query_parameter

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. It only states 'Add URL normalization parameter,' which implies a mutation but doesn't clarify permissions, side effects (e.g., impact on URLs), rate limits, or what 'normalization' entails. This is inadequate for a tool that likely modifies site settings, leaving critical behavioral traits unspecified.

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 a single, concise sentence with no wasted words. It's front-loaded and efficiently states the core action, though this brevity comes at the cost of clarity and completeness.

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 the tool's likely complexity (mutating site settings with 2 parameters), lack of annotations, 0% schema coverage, and no output schema details provided, the description is severely incomplete. It doesn't cover purpose, usage, parameters, or behavior adequately, making it insufficient for an agent to understand or invoke the tool correctly.

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 the input schema provides no descriptions for parameters 'site_url' and 'parameter.' The description adds no meaning beyond the generic 'URL normalization parameter,' failing to explain what these parameters represent (e.g., site_url as a target site, parameter as a query key/value) or their expected formats. This leaves both parameters entirely undocumented.

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 'Add URL normalization parameter' is vague and tautological—it essentially restates the tool name 'add_query_parameter' without specifying what 'URL normalization' means or what resource is being modified. It doesn't distinguish this tool from sibling tools like 'enable_disable_query_parameter' or 'remove_query_parameter', leaving the purpose unclear beyond a generic 'add' action.

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 doesn't mention prerequisites, context (e.g., for site management), or exclusions, and fails to reference sibling tools like 'enable_disable_query_parameter' or 'remove_query_parameter' for comparison. This leaves the agent with no usage direction.

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