github_update_topics

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

No annotations are provided, so the description carries full burden of behavioral disclosure. It clearly discloses that this is a destructive/replace operation ('replaces all existing topics'), which is critical for an agent to know. It doesn't state whether it requires authentication (likely via session_name) but the replacement semantics are the most important behavioral trait and are clearly disclosed.

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 compact with a one-line summary followed by labeled Args. The replacement warning is front-loaded. Each line in the Args section adds value. Slightly verbose for experienced users, but the structure is logical and efficient.

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 a mutation with no annotations and 0% schema coverage, so the description must carry substantial weight. It discloses the destructive replace behavior and documents all 4 params with brief semantics. However, it doesn't mention prerequisites (e.g., connection/auth required), response format, whether topics have validation constraints (length, format), or interaction with the session system. Acceptable but has gaps for a mutation tool.

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 param details are absent from the schema itself. The description provides an example format for topics ('python,mcp,devops') and labels what each arg is in the Args section (owner='Repository owner', repo='Repository name', etc.). This compensates partially. However, session_name's semantics are thin ('GitHub session to use') and it doesn't clarify whether it's optional or how sessions map to accounts.

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 states 'Set repository topics/tags (replaces all existing topics)' — a specific verb (Set) with resource (repository topics) and a key scope detail that it replaces existing topics. It distinguishes adequately from sibling github_list_topics by implying this is a write operation versus a read/list operation, though it doesn't explicitly name the alternative.

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 explicitly warns about the destructive nature ('replaces all existing topics'), which is a critical usage consideration. However, it doesn't explicitly state when to use this vs alternatives like github_list_topics (e.g., 'use list_topics to view before updating'). The usage guidance is implied by the replacement warning rather than explicit.

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