scm_repositories_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 behavioral burden, but it only exposes the HTTP verb 'GET', which weakly implies a non-mutating read. It says nothing about pagination behavior (despite a 'limit' parameter), authentication requirements, rate limits, or default result size — all material for a collection endpoint.

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 single line is short but wastes its only sentence by duplicating the route twice in parentheses. This is under-specification rather than genuine conciseness — brevity is achieved by omitting information an agent needs, not by removing filler.

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 six-parameter collection endpoint with no output schema and no annotations, the definition is far too thin. It leaves an agent without the basics: that it returns a paginated list of SCM repositories, how filtering via filter_id interacts with include/fields_* sparse fieldsets, or what the collection contains relative to scm_repositories_get_instance.

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 all six parameters (limit, include, filter_id, fields_*) are already documented in the schema. The description adds no syntax, defaults, or interaction hints beyond that, 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 literally just the HTTP route "GET /v1/scmRepositories (GET /v1/scmRepositories)", which restates the tool name rather than describing the purpose in prose. An agent can infer it lists SCM repository resources, but only by decoding the name and route — no verb+resource statement is given, and it is not distinguished from siblings such as scm_repositories_get_instance or scm_providers_repositories_get_to_many_related.

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 usage guidance whatsoever: no when-to-use, no when-not-to-use, no mention of the sibling retrieval tools it competes with. Nothing in the text helps an agent decide between this collection endpoint and the to-one/to-many relationship variants.

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