Api representatives cascade info retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description contributes only the word "preview," which hints the call is a non-committal look at cascade effects, but it discloses nothing about what data is returned, whether the object must exist, or how deep the cascade traversal goes.

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?

Two words with a trailing colon is technically concise but is under-specification, not conciseness; it reads as a truncated fragment rather than a front-loaded summary. Nothing here earns or fills space.

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?

No output schema, zero schema description coverage, and a two-word description leave the agent without any basis for interpreting the response or the id. For a retrieval endpoint whose entire value is the shape of the preview payload, this is inadequate.

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?

There is exactly one required parameter, `id`, and schema description coverage is 0%, so the description carries the burden of explaining it — and it says nothing. It does not state which object the id refers to (a representative, presumably) or what happens if the id is unknown. The bare mention of "cascade" is the only indirect signal.

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?

"Cascade preview:" names neither a clear verb nor what is being previewed or returned. It gestures at a cascade/impact preview for representatives, but an agent cannot tell from this fragment whether it computes deletion impact, dependency listing, or something else. Among dozens of near-identical `*_cascade_info_retrieve` siblings, this gives no way to confirm the resource semantics beyond the tool name itself.

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 whatsoever on when to call this versus `representatives_retrieve`, `representatives_object_retrieve`, or `representatives_destroy`. The label "preview" faintly implies pre-deletion inspection, but that is inference, not instruction.

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