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

Annotations already declare the safe read-only, open-world profile, and the description adds a materially important trait not in structured data: a per-call cost of $0.002 USDC on Base. It also notes the data is sanitized with README summaries, giving useful context on result quality.

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 compact sentences, front-loading the resource and scope before the price detail. No filler or redundancy.

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 zero-parameter feed with an output schema and annotations in place, the description covers scope, cost, and data provenance adequately. Minor omission: it doesn't state how many repositories are returned or the exact time window beyond 'today'.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Schema coverage is also effectively complete with an empty property set.

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 states a specific resource ('Top trending GitHub AI agent & MCP tool repositories') and scope ('today'), which clearly separates it from sibling feeds like arxiv_agent_papers and hackernews_ai_digest. It lacks an explicit verb ('list'/'fetch'), but the noun phrase makes the operation unambiguous.

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 choose this over siblings such as hackernews_ai_digest or arxiv_agent_papers, and no stated preconditions. Usage is only implied by the resource described.

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