enable_disable_query_parameter

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Enable or disable' implies a mutation operation, the description doesn't specify what this operation actually does (does it toggle a setting? apply to all pages?), what permissions are required, whether changes are reversible, or what the expected outcome is. This leaves significant behavioral gaps for a mutation tool.

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, efficient sentence that states the core functionality without unnecessary words. It's appropriately sized for what it communicates, though it could benefit from additional context given the tool's complexity.

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?

For a mutation tool with 3 undocumented parameters, no annotations, and sibling tools that handle related operations, the description is insufficient. While an output schema exists (which reduces the need to describe return values), the description doesn't provide enough context about the operation's behavior, parameter meanings, or differentiation from alternatives to be considered complete.

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 0% description coverage, so all three parameters are undocumented in the schema. The description mentions 'URL query parameter' which hints at the 'parameter' field, but doesn't explain what 'site_url' represents, what format it expects, or what the 'enabled' boolean actually controls. The description adds minimal semantic value beyond what's implied by parameter names.

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 ('Enable or disable') and the target resource ('a URL query parameter'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from sibling tools like 'add_query_parameter' or 'remove_query_parameter', which handle related but different operations on query parameters.

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's no mention of prerequisites, when this operation is appropriate, or how it differs from sibling tools like 'add_query_parameter' or 'remove_query_parameter' that also manage query parameters.

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