update-glossary

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

With no annotations, the description bears full responsibility for behavioral transparency. It only states the method (JSON Patch) but does not disclose whether updates are partial, atomic, require specific permissions, or affect linked entities. No side effects or constraints are mentioned.

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 brief sentence, which is concise but lacks crucial details. It is front-loaded but too minimal for a tool that likely requires more context about JSON Patch usage.

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?

Despite having only two parameters and no output schema, the description fails to provide context about the operation, such as return values, success criteria, or dependencies (e.g., glossary must exist). Compared to the many sibling tools, it is incomplete.

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%, and the schema already describes the 'id' as 'Glossary UUID' and 'operations' as 'JSON Patch operations'. The description merely repeats 'using JSON Patch operations', adding no semantic value beyond 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 states it updates a glossary using JSON Patch operations. The verb 'update' and resource 'glossary' are specific, and the method 'JSON Patch' is mentioned. However, it does not differentiate from sibling tools like update-glossary-term, though the resource name helps.

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 create-glossary, delete-glossary, or other update tools. There is no mention of prerequisites or context.

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