Api representatives update

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

Annotations already state readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is partly covered. However, the description adds no behavioral context: it does not say what editing means, whether the body replaces the resource, what permissions are needed, or how partial updates differ. 'Viewed or edited' is boilerplate and does not meaningfully supplement the annotations.

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 sentence with no unnecessary length, but it is generic boilerplate rather than a front-loaded, informative statement of purpose. It is concise but does not earn its place with useful information.

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?

This is a mutation endpoint with two parameters, one of which is an unconstrained body object, and the description provides essentially no context. With no output schema and no schema descriptions, an agent cannot learn from the description what the body should contain or what behavior to expect.

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 both parameters are effectively undocumented. The description does not explain that id identifies the representative or what the untyped body object should contain, so it fails to compensate for the low coverage.

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 says only that this is an 'API endpoint' where 'representatives' can be 'viewed or edited,' which mixes read and write semantics instead of clearly stating that the tool updates a representative. The name and title imply update, but the description itself does not distinguish this from sibling tools like representatives_retrieve, representatives_partial_update, or representatives_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?

There is no guidance on when to use this tool rather than representatives_partial_update, representatives_update, or representatives_retrieve. The phrase 'viewed or edited' implies possible usage but does not set any explicit condition, prerequisite, or exclusion.

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