scm_providers_repositories_get_to_many_related

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing: not pagination behavior (limit), not the include/fields expansion semantics, not auth or rate-limit expectations. A bare endpoint string is not 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?

It is short, but not because it is efficient — it is under-specified and wastes the entire space by repeating the same endpoint string twice inside parentheses. Nothing is front-loaded because nothing is stated.

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?

A GET endpoint with 7 query parameters, no annotations, and no output schema needs the description to explain pagination, relationship inclusion, and field selection. None of that is present, leaving the agent with only a URL template.

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% and all 7 parameters (id, limit, include, filter_id, and the three fields_* selectors) are documented in the schema itself. The description adds no additional meaning, so the baseline of 3 applies.

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 is just the raw HTTP path restated, and then duplicated in parentheses. It does name the resource (scmProviders/{id}/repositories), so an agent can infer a list operation, but there is no natural-language verb+resource statement and no differentiation from the sibling scm_providers_repositories_get_to_many_relationship.

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?

No when-to-use guidance, no prerequisites, and no mention of the near-identical sibling '..._get_to_many_relationship' that the agent must choose between. The REST path alone gives no selection criteria.

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