mock_route

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

With no annotations, the description carries the full burden of behavioral disclosure. It states 'Mock network requests' implying interception and response, but does not specify duration, persistence, side effects, or that it overrides actual requests. The output schema exists but is not utilized to explain behavior.

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 very short (one sentence), which is concise but lacks necessary detail for a tool with four parameters. It is not wasteful, but the brevity harms 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 has four parameters, no schema descriptions, no annotations, and an output schema, the description is severely incomplete. It fails to explain how to construct mocks, prerequisites, or what the output represents.

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 explain parameter semantics. Only url_pattern is mentioned; status, body, and content_type are entirely undocumented. No guidance on formatting body or valid values is provided, making parameter usage unclear.

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 verb 'Mock' and the resource 'network requests matching url_pattern', which is specific and distinguishes it from sibling tools like clear_route or abort_route. However, it does not elaborate on what 'mock' entails beyond matching, leaving some ambiguity.

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 is provided on when to use this tool versus alternatives such as clear_route or abort_route. There is no mention of context (e.g., before navigating) or when not to use it.

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