Create mock from request

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the agent knows this mutates state non-idempotently, and the description's 'before persisting' confirms a new artifact is written. It does not state that repeated calls create duplicate rules or describe what is returned, so it adds only modest context beyond the annotations.

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?

Two tightly written sentences with the composite fetch-then-create behavior front-loaded and no wasted words. Efficient and easy to parse, though the 'Convenience:' prefix is slightly informal filler.

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 state-creating tool with no output schema, the description covers the mechanism (fetch by id, scaffold from recorded response, apply overrides) but omits what the call returns and how duplicates/non-idempotency are handled. Adequate but with visible gaps for a mutation tool.

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 coverage is 100%, so all four parameters are already documented in the schema. The description's note about 'optional overrides let the caller tweak fields' usefully frames why name/url_pattern/dynamic exist, but adds no syntax or default detail beyond what the schema provides, matching the baseline 3.

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 a specific composite verb+resource: fetch a captured request by id and scaffold a mock rule from its recorded response. This is clearly richer than a plain 'create mock' and distinguishes it conceptually from siblings like create_mock_rule, but it never explicitly names that alternative, so an agent must still infer which to pick.

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 leading word 'Convenience' implies the use case (scaffolding a mock from an existing captured request rather than authoring one from scratch), which is implied guidance. However, it never states when-not to use it or names the alternative (create_mock_rule, or get_request followed by manual creation), leaving selection partly to inference.

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