Update Company Form Template

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

Annotations already indicate the tool is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds that only supplied fields are changed and returns the modified object, which provides useful partial update behavior. However, it omits potential side effects, authorization requirements, or error conditions, leaving some gaps beyond what annotations cover.

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 well-structured with a clear title, usage instruction, behavior, required params, and API info. It is concise but not overly terse, earning a 4.

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 simple update tool with a rich schema and no output schema, the description covers the essential aspects: purpose, required params, partial update behavior, and return value. It is adequately complete for agent decision-making, though it could mention error handling or validation.

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 the baseline is 3. The description adds value by highlighting required parameters and emphasizing that only supplied fields are updated, but it does not provide additional meaning 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 states 'Update Company Form Template' and distinguishes itself from sibling tools like create, show, and delete. It specifies the action 'update an existing Forms' and provides the exact endpoint, 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 tells the agent to use this tool for updating existing forms and lists required parameters. However, it does not explicitly mention when not to use it or suggest alternatives. Given the sibling context, this is clear but could be more explicit.

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