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

With no annotations, the description carries the full burden. 'Value discarded' does disclose a useful non-persistence trait, but it is asserted only for the topic slug while the schema implies the same for eight other domains, and nothing is said about return shape, error behavior, or whether any check is strict. A single fragment cannot cover a nine-parameter tool with zero annotation support.

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?

It is short and front-loaded, but for a nine-parameter tool the single seven-word fragment is under-specified rather than concise. Brevity here reflects missing content, not economy.

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?

No annotations, no output schema, nine parameters spanning unrelated domains, and a description that addresses only the GitHub-topic case. Nothing reconciles the name/schema mismatch or tells an agent what a call returns, so the definition is materially incomplete.

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 100%, so each parameter is already documented in the schema, which sets the baseline at 3. The description adds no format, validation-rule, or interaction detail beyond the schema and in fact covers only one of the nine parameters.

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 names a specific resource ('GitHub topic slug') and a specific check ('charset'), which is more than a tautology. But it does not account for the nine wildly unrelated parameters (city, zone, feed, json, path) the schema actually accepts, so an agent cannot tell what this tool really does. The purpose is stated but only for a fraction of the tool's apparent surface.

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?

There is no when-to-use, when-not-to-use, or routing guidance at all. Siblings like github-repo-shape, jira-key-shape, file-path-ok, iana-zones and validate-json clearly overlap with individual parameters here, yet the description never says whether this tool replaces or complements them.

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