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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It offers no details about read-only nature, authentication, rate limits, or output format, leaving the agent without critical operational context.

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, short fragment. While it is concise, it lacks structure and fails to front-load actionable information. It reads more like a label than a functional description, and its brevity comes at the cost of essential detail.

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 tool with one parameter and an output schema, this description is grossly incomplete. It does not explain how to use the tool, what the parameter does, or any operational constraints. An agent cannot make an informed call with this minimal context.

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 single parameter 'q' has 0% schema description coverage, and the description does not explain what 'q' represents. Whether it is a username, query string, or something else is completely ambiguous, making correct invocation impossible without external knowledge.

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 is a noun phrase 'A user's public gists' that names the resource but lacks an explicit verb. It doesn't clarify whether the tool lists, searches, or retrieves gists, and it doesn't distinguish it from siblings like 'ghgists' or 'github'. An agent cannot confidently determine the exact action from this description.

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 guidance on when to use this tool versus alternatives. No mention of prerequisites, exclusions, or alternative tools is provided, leaving the agent to guess based on the name and context.

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