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

There are no annotations, so the description carries the full burden of behavioral disclosure. It implies a read-only retrieval of public gists, but it does not state whether authentication is needed, how results are paginated, what happens with an empty query, or whether the tool fetches gists for a specific user or searches across all public gists.

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 very short, which is economical, but it is under-specified rather than appropriately concise. It spends its single sentence restating the resource name without providing the operational details—especially parameter semantics—that an agent needs.

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?

Although the tool is simple and has an output schema, the description omits the meaning of the only input parameter and leaves the tool's exact purpose ambiguous between user-specific gists and query-based search. This is a critical gap in an otherwise simple tool, so the description is not complete enough for correct invocation.

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 input schema has one parameter, 'q', with 0% schema description coverage. The description never mentions 'q', its meaning, format, or expected values. Since the schema is bare and the description provides no compensatory parameter explanation, an agent cannot reliably determine what to pass in.

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 identifies the resource as 'GitHub Gists: Public gists for a user,' which names the domain and object type. However, it lacks a specific verb (e.g., 'retrieve,' 'search,' 'list') and does not clarify whether the tool finds gists by user, query, or both. It also does not differentiate itself from the sibling tool 'githubgists,' leaving ambiguity about which tool to choose.

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 is given about when to use this tool versus alternatives like githubgists, githubsearch, or github_code. The phrase 'for a user' weakly implies a lookup scenario, but with no explicit context or exclusions, an agent has little basis for deciding to invoke it.

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