Api representatives object retrieve

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

The description claims the endpoint allows representatives to be 'viewed or edited', but annotations declare readOnlyHint=true and destructiveHint=false for a retrieve-style, id-only operation. Claiming edit capability directly contradicts the declared safety profile and would mislead an agent about mutation risk.

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 short sentence, so it is not bloated. But it spends its one clause on a generic and partly wrong boilerplate claim ('viewed or edited') rather than front-loading useful retrieval 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?

For an object-retrieval tool with no output schema and one undocumented parameter, the description should state that it returns a single representative's details by id. Instead it offers generic DRF boilerplate that omits return shape and contradicts the read-only annotation.

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 single 'id' parameter is undocumented in both schema and description. The description says nothing about what the id identifies (representative record identifier, its type, or format), so it fails to compensate for the coverage gap.

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 names the resource (representatives) and the general action (viewing), so the broad purpose is inferable. However, it adds no scope detail (single object vs list, lookup by id) and does nothing to separate this tool from the crowded family of siblings such as representatives_list, representatives_retrieve, representatives_object_retrieve and representatives_cascade_info_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 call this endpoint versus the many alternatives on the representatives resource. The only signal the agent gets is the required 'id' parameter in the schema, which is structural rather than descriptive.

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