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

Annotations already declare this a safe, idempotent, closed-world read, so the description is free to add genuine behavioral context: a 6-hour refresh cadence, the fact that ranking is star-only with no museum vetting, and an explicit safety instruction not to install/clone/run results unreviewed. Those are traits no annotation or schema field carries, and they materially change how an agent should present the data.

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?

Three sentences, each doing distinct work: what it returns, how fresh it is, and the vetting/safety caveat. The core capability is front-loaded and no sentence is redundant.

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?

With no output schema, the description compensates by listing the returned fields (name, description, stars, language, URL). For a zero-required-parameter read tool, freshness, ranking basis and the safety caveat cover everything an agent needs to call and present it correctly.

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%, with both `limit` (min/max/default) and `visitor_name` fully documented inline, so the baseline is 3. The description adds nothing about either parameter — no mention of the 15-item default or that `limit` is optional, and no note that `visitor_name` is unnecessary for this read.

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?

"Get the most-starred new GitHub repositories (created in the last 30 days) about AI agents, LLMs and MCP" gives a specific verb, resource, ranking criterion, recency window and topic scope in one sentence. It also enumerates the returned fields, so an agent knows exactly what it gets without opening the schema.

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?

Usage context is implied by the topic scope (AI agents/LLMs/MCP) and the recency filter, and the closing caveat tells the agent to route results through the user's review. However, it never states when to prefer this over the closest sibling, tech_news, nor any exclusion conditions. Adequate but with a clear routing gap.

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