List active transform rules

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. The description only says 'View' which implies a read-only operation, but doesn't describe the return format, whether the output is structured or free-form, pagination, or any side effects. For a read-only tool with no annotation fallback, this is thin.

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?

A single concise sentence that states the purpose clearly with zero filler words. Every word 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?

For a zero-parameter read-only tool, the description is functionally adequate for invoking the tool. However, with no output schema and no annotation coverage, it lacks behavioral context entirely. The agent cannot know what the response will contain, which matters given the many sibling tools that might produce similar-looking 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?

The tool has 0 parameters with 100% schema coverage (empty schema properties). Since there are no parameters to document, the description doesn't need to add parameter semantics. Baseline of 4 for a 0-parameter tool is appropriate.

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 'View the active intercept-and-transform rules' states a clear verb (View) and specific resource (active intercept-and-transform rules). It distinguishes from siblings like proxy_list_request_transforms and proxy_list_mocks by specifying 'intercept-and-transform rules'. Could be slightly clearer about what distinguishes 'transform rules' from request transforms, but the purpose is clear.

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 vs alternatives. With 18 siblings including proxy_list_request_transforms, proxy_list_mocks, and proxy_list_traffic, the description does not help an agent choose between listing transforms versus request transforms versus mocks. No when/when-not guidance or exclusions provided.

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