recommend_repositories

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'recommends' but does not explicitly confirm it is read-only, mention authentication requirements, or explain how interests are derived. This lack of detail leaves significant behavioral ambiguity.

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 two sentences with a simple argument list, no redundant content, and the main purpose is front-loaded. It is appropriately sized for a tool with one parameter.

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 has one parameter and an output schema, the description is moderately complete. It explains purpose and the argument, but lacks context on what 'interests' means, how recommendations are generated, or any limitations. The presence of an output schema mitigates the need to describe return values, but more context would still help.

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 0%, so the description must compensate. It adds the line 'username: The GitHub username to analyze,' which gives some meaning beyond the bare schema name. However, this is minimal—it does not clarify format, whether it is a login or ID, or any other constraints.

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 clearly states the tool's function: 'Recommend new repositories to a developer based on their interests.' It uses a specific verb ('Recommend'), identifies the resource ('new repositories'), and specifies the context ('based on their interests'), distinguishing it from siblings like analyze_developer or list_user_repositories.

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 implies the usage context—an agent should call this when a developer wants repository recommendations based on their interests. However, it does not explicitly compare with alternatives or mention when not to use it, leaving the guidance at an implied level rather than explicit.

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