Update Program

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

Annotations already indicate non-read-only and non-destructive behavior. The description adds that only supplied fields are changed and returns the modified object, which is useful but does not disclose side effects, authorization needs, or the contradiction between openWorldHint and additionalProperties: false in the schema.

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 contains 4 sentences. It starts clearly but includes redundant phrases like 'Use this to update an existing Company Settings' and repeats the return behavior. It could be more compact while retaining key points.

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 6 parameters and no output schema, the description adequately states the action, required fields, and return value. However, it lacks details on error handling, idempotency, or limitations. Overall, it covers the basics but is not exhaustive.

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 reiterates required parameters (company_id, id) but adds no additional meaning or constraints beyond the schema. The general PATCH behavior is stated but not per-parameter.

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 the specified Program' with a specific verb and resource. It distinguishes from sibling tools like create_program and delete_program by context. However, referring to 'Company Settings' creates minor ambiguity about the resource type.

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 mentions required parameters and the general update action but does not provide explicit guidance on when to use this tool versus alternatives like create, delete, list, or show. No exclusionary criteria or context for selection.

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