ise_ers_patch

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. It implicitly indicates mutation (PATCH/update) but doesn't state what happens on partial field omission, whether it returns the updated object, validation behavior, or error handling for non-existent IDs. For a mutation tool with zero annotation coverage, this is a notable gap.

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 conveys the operation type, scope, and a key usage instruction. Zero waste, all content is load-bearing for the purpose and usage guidance.

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?

This is a dangerous mutation operation with 4 parameters, no output schema, and no annotations. The description adequately communicates the core purpose and partial-update guidance, but for a write operation of this breadth (60+ resource types), more behavior disclosure would be warranted. The description is adequate but modest given the tool's complexity and risk profile.

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 75%, with 'data' and 'deployment' having descriptions and 'resource' having a description plus enum. The description's 'Provide only the fields to change' clause adds meaning to the 'data' parameter beyond its bare 'Fields to change' schema text by emphasizing the partial-update semantics. However, 'id' has no schema description, and the description doesn't add format or constraint detail beyond what the schema provides.

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 it performs a 'Partial update (PATCH) of an existing ERS object by ID,' specifying the verb (PATCH/update), resource (ERS object), scope (single object by ID), and the ISE version constraint (ISE 3.x). This clearly distinguishes it from siblings like ise_ers_create (full create), ise_ers_update (full update), and ise_ers_get (read).

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 states 'Provide only the fields to change,' which gives useful guidance on how to use the tool (partial vs full update). However, it doesn't explicitly distinguish when to use PATCH vs the sibling ise_ers_update tool, nor does it mention any prerequisites like needing to fetch the existing object first. The ISE 3.x version constraint is mentioned but not elaborated.

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