add_repository_topics

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

No annotations are provided, so the description carries the full burden. It discloses one behavioral trait: topics are added without removal. However, it omits other important aspects such as authorization requirements, idempotency (duplicate topics), rate limits, or side effects.

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 a single, efficient sentence that conveys the core purpose and key constraint without any fluff or redundant phrasing. It earns its place.

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 relatively simple tool with 3 parameters and no output schema, the description is minimally adequate. It covers the fundamental behavior but lacks details on return values, error handling, and the optional owner parameter. A bit more completeness would be helpful.

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%, and the description offers no additional information about the parameters (owner, repo, topics). The description does not clarify what 'owner' is (despite being optional), the format of topics, or any constraints beyond the schema, leaving the agent with minimal guidance.

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 topics/tags to a repository') and includes a key constraint ('without removing existing topics'), which distinguishes it from sibling tools like 'add_repository_labels' that handle labels instead of topics.

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 implicitly informs when to use this tool (when you want to add topics without overwriting existing ones) but does not explicitly state alternatives or when not to use it. Sibling tools exist (e.g., 'add_repository_labels'), but no comparative guidance is provided.

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