add_repo

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

With no annotations, the description carries the full burden for behavioral disclosure. It adds valuable context: the repo is verified for existence and accessibility, and the save persists across sessions. It does not mention idempotency (e.g., what happens if the repo is already saved) or error handling, but the disclosed behavior is meaningful and not contradicted by any annotations.

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?

Two concise sentences with no wasted words. The first sentence states the purpose, the second provides the key usage detail and a behavioral note. Well-structured and front-loaded.

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?

The tool is simple (one parameter) with no output schema and no annotations. The description covers purpose, persistence, verification, and format. It could have added notes on duplicate handling or errors, but for the simplicity of the operation, the description is largely complete.

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?

The schema description covers the parameter fully (100% coverage), explaining the 'owner/repo' format and giving an example. The description repeats the format but adds no new parameter semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 action ('Add a GitHub repository to the saved list') with a specific verb and resource, and distinguishes it from siblings like list_repos and remove_repo. The scope is 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 explains the persistence benefit ('accessible in this and all future sessions') and the required owner/repo format, which implies when to use it. It does not explicitly state when not to use it or name alternative tools, but the sibling set and clear purpose make the context obvious.

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