update-stored-procedure

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

The description only states 'Update' and the use of JSON Patch, leaving out key behavioral details such as side effects, authorization requirements, error handling (e.g., if the procedure doesn't exist), or confirmation of partial update semantics.

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 concise (one sentence, 7 words) and front-loaded. It earns its place, but could potentially include a word like 'partially' without harm.

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?

With no output schema and low complexity, the description is somewhat complete but lacks explanation of return values, error conditions, or how it relates to sibling tools. Adequate but not thorough.

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 schema already covers both parameters with descriptions. The description reinforces 'JSON Patch operations' but adds minimal new information beyond what is already in the schema.

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 identifies the action (Update), the resource (a stored procedure), and the method (JSON Patch operations). It is specific enough to distinguish from many siblings, though it does not explicitly highlight that this is a partial update.

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 about when to use this tool versus alternatives like create-stored-procedure or other update tools. There is no mention of prerequisites or when JSON Patch is preferred.

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