update_collection_request

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

No annotations are provided, so the description must fully convey behavioral traits. It indicates mutation ('Update') and a constraint ('Cannot change request folder'), but fails to disclose other important aspects: permissions required, whether updates are partial or full, or what the response looks like. Given the absence of annotations, this is insufficient.

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 extremely concise: two sentences with no extraneous information. It front-loades the core action and then adds the key limitation. 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 mutation tool with three parameters and no output schema, the description provides the core purpose and a notable limitation. However, it omits details like whether the update is partial or overwrites all fields, and what the expected response is. While not severely incomplete, it could be more informative.

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%—all three parameters have descriptions in the input schema. The description adds no additional meaning beyond what the schema already provides (e.g., it does not clarify the format of the request object or constraints on name/method/url). Baseline score of 3 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 clearly states 'Update a request in a collection' with a specific verb and resource. It also adds a constraint ('Cannot change request folder'), which distinguishes this tool from other operations like moving or creating requests. Sibling tools include create, delete, and get requests, making the purpose unambiguous.

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 implicitly hints at when not to use this tool (e.g., if you need to change the folder, use a different tool). However, it does not explicitly state when to use this tool over alternatives, provide prerequisites, or mention typical use cases. The guidance is minimal and inferential.

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