scm_providers_get_collection

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

No annotations are provided, so the description carries the full burden and discloses nothing: no auth/permission requirements, no pagination semantics despite a limit parameter, no statement about what is returned or whether it is a safe read. The redundant path string adds 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?

It is short but not concise in the meaningful sense: the same endpoint string is duplicated inside parentheses, adding no information. Under-specification rather than economy.

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 list endpoint with no annotations and no output schema, the description should at minimum explain what an SCM provider is, the pagination model, and how the fields parameter shapes the response. None of that is present, leaving the agent unable to use the tool reliably.

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%, so the schema already documents limit ("maximum resources per page") and fields_scmProviders (including the enum of selectable fields). Per the rubric, high coverage sets a baseline of 3 even with no parameter discussion in the description. The description adds nothing further, so it does not exceed that baseline.

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 literally restates the endpoint path twice: "GET /v1/scmProviders (GET /v1/scmProviders)". It is a tautology that repeats the tool name's verb and resource without saying what an SCM provider is or what the collection returns. It also fails to distinguish itself from siblings like scm_providers_get_instance or scm_repositories_get_collection.

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 mention of alternatives, no prerequisites. An agent cannot tell from this text whether to call this to enumerate all providers, whether pagination is needed, or how it differs from scm_providers_get_instance.

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