List Git repositories

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds behavioral value by stating the scope behavior ('when no project is given') and the return contents ('default branch and URLs'), which is useful since there is no output schema. This is beyond what the annotations alone provide, though it does not discuss pagination or permissions.

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?

A single sentence conveys purpose, scope, conditional behavior, and expected output fields with no filler. The key information about scope is front-loaded before the output note.

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 simple, read-only, idempotent list operation with one optional parameter, the description together with the schema and annotations is complete. It addresses what is returned, how scope is controlled, and the operation's non-mutating nature via annotations.

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 coverage is 100%, so the baseline is 3. The parameter description already contains the omit/unset TFS_DEFAULT_PROJECT behavior, and the tool description mostly rephrases this rather than adding new semantic meaning. No additional parameter syntax, format, or constraint details are introduced beyond the 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 uses a specific verb and resource: 'List Git repositories' with a clear scope ('in a project or in the whole collection'). It explicitly mentions the output fields ('default branch and URLs'), which further distinguishes it from sibling tools like get_file_content or list_directory.

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?

The description gives clear context on when to use: list repositories in a project, or when no project is given, in the whole collection. It does not explicitly name alternatives, but there are no repository-listing siblings, so the exclusion criteria are less necessary. It stops short of a 5 because it does not state when not to use this tool versus another.

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