github_list_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 does not disclose whether the list is sorted, paginated, whether empty repos return empty lists, what the output format is (though output schema exists), or any read-only characterization. The conflation of topics/tags adds 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 short and compact, but the Args block duplicates what the schema already provides without adding value. The format is acceptable but the content is thin; it is concise but under-informative rather than efficiently informative.

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?

Despite having an output schema, the description is very thin for a GitHub tool. It does not clarify the topics/tags distinction (critical given github_list_tags exists), mention pagination limits (topics have a 20-topic limit on GitHub), or explain edge cases for empty lists. For a tool with 0% schema coverage and no annotations, this is insufficient.

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 for the three parameters. The description lists parameter names in an Args block but adds no meaning beyond the names themselves. It does not explain what owner/repo must be (e.g., URL-encoded, case-sensitivity) or what session_name does (though it has a default). The Args block merely echoes the schema.

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 'Get repository topics/tags' which identifies the verb (get) and resource (repository topics/tags). However, it conflates 'topics' and 'tags' which are distinct GitHub concepts, and the sibling github_list_tags exists for tags. This creates ambiguity about whether it returns topics, tags, or both.

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?

No guidance on when to use this tool vs alternatives. The description does not distinguish from github_list_tags or github_update_topics, nor does it clarify whether to use this for viewing topics vs tags. There is no mention of when this is appropriate versus sibling tools.

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