List repositories with filtering and pagination options.

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds the 'CALL IMMEDIATELY' reassurance but no additional behavioral details beyond what is in the annotations. It is adequate but not richly transparent.

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 description is extremely concise (two sentences) and front-loaded with the purpose. Every word earns its place; the emoji and directive are efficient. No wasted text.

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?

Given the tool's simplicity (no required params, output schema exists), the description is largely complete. It could mention that it returns a list of repository objects, but the output schema likely covers that. Annotations and schema fill remaining gaps.

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?

All parameters are described in the schema with 100% coverage, providing defaults and descriptions. The description adds no extra semantic meaning beyond 'filtering and pagination options,' which is generic. The schema already handles parameter semantics.

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 title and description clearly state the tool lists repositories with filtering and pagination, distinguishing it from sibling tools which operate on different resources (advisor, inventory, etc.). The verb 'list' and resource 'repositories' are specific and unambiguous.

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 includes 'CALL IMMEDIATELY - No information gathering required,' which strongly indicates it is safe to use without prerequisites, but it fails to provide explicit guidance on when not to use it or alternatives. The usage context is implied rather than explicit.

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