Api representatives partial update

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

Annotations already disclose readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds no behavioral context beyond "edited"—it does not mention partial-update semantics, required id targeting, body contents, permissions, or what happens to omitted fields.

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?

It is a single front-loaded sentence with no bloat, but the sentence is generic boilerplate that fails to earn its place by conveying useful tool behavior.

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?

With no output schema, 0% parameter description coverage, and a generic object body, the description is far too thin for a mutation endpoint. It does not explain enough for an agent to safely construct a partial update request.

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 never mentions the required id or the opaque body parameter. For a two-parameter tool with an underspecified body object, this leaves the agent with no semantic guidance beyond parameter names.

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 states a resource (representatives) but uses generic boilerplate, "API endpoint that allows representatives to be viewed or edited." It does not clarify that this is specifically a partial update, nor does it differentiate the tool from siblings such as representatives_update, representatives_create, or representatives_retrieve.

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 partial update versus the full update, create, retrieve, or list tools. The phrase "viewed or edited" is actively misleading for an endpoint whose name indicates only partial mutation.

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