github_gists_get

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

No annotations provided, and the description does not disclose any behavioral traits beyond the basic action. It fails to mention that this is a read-only operation, that authentication may be required, or what the response contains. The description carries the full burden for behavioral disclosure and does not meet it.

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?

At three words, the description is extremely concise and front-loaded. While it lacks structure, the brevity is appropriate for a simple get operation. Every word is necessary, but there is room to add context without becoming verbose.

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?

Given the tool's simplicity (one parameter, no output schema), the description is just adequate. It covers the core purpose but omits context like return value or relationship to similar tools. A more complete description would mention that it returns the full gist object for the given ID.

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?

With 100% schema description coverage, the baseline is 3. The description provides no additional meaning beyond the schema's 'gist_id' parameter; it does not explain the format or purpose of the parameter. However, the schema already documents it adequately.

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 'Get a gist' is a clear verb+resource combination that directly states the tool's action. It distinguishes well from siblings like github_gists_list (list all) and github_gists_get_revision (get revision).

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 versus alternatives like github_gists_list or github_gists_get_revision. The description doesn't mention typical use cases or scenarios, leaving the agent to infer based on name alone.

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