Api representatives create

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

Annotations already disclose that this is a non-read-only, non-idempotent, non-destructive, open-world write operation. The description adds little beyond saying the endpoint allows viewing or editing, and it does not explain the create behavior, required permissions, or what happens on success.

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 only one sentence, so it is concise, but it is neither front-loaded around creation nor informative. The sentence does not earn its place because it omits the action implied by the tool name.

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 and one undocumented body parameter, the description must carry the burden of explaining the create operation. It does not describe the expected payload, response, or operational context, leaving the definition materially incomplete.

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?

The only parameter is an untyped body object with 0% schema description coverage, and the description says nothing about its contents or required fields. For a create endpoint, this leaves the agent unable to construct a valid request from the definition.

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 the endpoint allows representatives to be "viewed or edited," which is generic and omits the tool's actual create action. It restates the resource but does not distinguish this create endpoint from sibling read or update endpoints.

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 versus alternatives such as representatives_list, representatives_retrieve, or representatives_update. It provides no context, exclusions, or prerequisites for creating a representative.

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