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

Discloses data source (cached), ranking order, and scope. No annotations provided, so description carries burden; it adds context about caching and ranking though omits potential staleness or authentication needs.

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?

Two sentences, front-loaded with core purpose and key constraints. No unnecessary details, every sentence adds value.

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?

Covers purpose, scope, parameters, and alternatives. Lacks output format details, but acceptable for a list tool with no output schema. Adequate for agent 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?

Adds meaning to two parameters with examples (e.g., 'celestiaorg/docs', 'Q&A'). Explains ranking context. Despite high schema coverage, description provides useful usage hints beyond 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?

Clearly states it lists GitHub Discussions from Celestia repos cached locally, ranked by upvotes then recency. Distinguishes from get_github_discussion (single thread) and get_discussion (community forum).

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?

Explicitly limits to Celestia repos and local cache, warns not for arbitrary GitHub Discussions, and directs to dedicated tools. Provides clear when-to-use and alternatives.

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