bundle_ids_profiles_get_to_many_relationship

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

With no annotations provided, the description carries the full behavioral burden, yet it discloses nothing about pagination (despite a limit parameter), authentication requirements, ordering, or the shape of the response. It is a bare endpoint string with zero behavioral context.

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 text is short but wastes its entire content by duplicating the same endpoint string verbatim in parentheses, adding zero information. It is under-specified rather than genuinely concise.

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 a relationship-list endpoint with no output schema, no annotations, and a vast sibling set of similar relationship tools, the description provides nothing an agent needs to invoke it correctly or interpret the result. It is wholly inadequate for the tool's complexity.

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 100% for both parameters ('id' and 'limit'), so the schema already documents their meaning. The description adds no semantics beyond what the schema provides, which is the baseline 3 for a fully-covered schema.

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 only restates the HTTP route ('GET /v1/bundleIds/{id}/relationships/profiles'), which technically encodes a verb and resource but gives no plain-language statement of what the tool returns or why an agent would call it. An agent must decode the URL path to infer that it lists the profiles related to a bundle ID.

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, no prerequisites, and no differentiation from near-identical siblings such as bundle_ids_profiles_get_to_many_related or profiles_bundle_id_get_to_one_relationship. Nothing tells the agent which of the many relationship endpoints to pick.

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