Update a routine

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

Annotations indicate this is a non-read-only, non-idempotent mutation. The description adds the authorization class ('board_or_agent'), which is useful, but does not disclose side effects, partial update behavior, or response details. With annotations already providing basic behavioral cues, the description adds moderate value.

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 short but lacks essential details. It is not verbose, but it sacrifices completeness for brevity. Every sentence serves a purpose, but more context is needed for a tool with many parameters.

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?

Given the tool's complexity (large input schema, many sibling tools), the description is insufficient. It does not explain what fields are updatable, that it is a partial update (PATCH), or any constraints. The output schema exists but the description adds no value.

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 0%, and the description provides no information about the body or path parameters. Given the complex schema with many fields under 'body', the absence of any parameter guidance makes the tool difficult to use correctly.

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 a routine', specifying the verb and resource. However, it does not distinguish this tool from its siblings like pc_get_routines_by_id or pc_post_companies_by_company_id_routines, missing an opportunity to differentiate.

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 lacks any guidance on when to use this tool versus alternatives. It does not mention prerequisites, when a routine can be updated, or contrast with create/delete operations.

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