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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the data source (GitHub Search API), daily refresh cadence, API-key requirement, and the side-effect that untracked repos get queued when passed via repo.

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?

Four short sentences, front-loaded with what the tool returns before moving to source, freshness, auth, and the single-repo mode. Dense but no filler; the parenthetical source note is the only mildly extraneous element.

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 no-required-param, no-output-schema feed tool, the description covers source, freshness, auth, and the single-repo path. The main omission is pagination behavior (limit/offset) for the full feed, which an agent would need to page results 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 coverage is only 40%, with q and since documented but repo, limit, and offset bare. The description compensates for repo by explaining the owner/name format and queueing, but says nothing about limit/offset pagination semantics, leaving half the parameters unexplained in both places.

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 names a specific resource and verb: a feed of GitHub AI agent & MCP repos sourced from the GitHub Search API, refreshed daily. It differentiates reasonably from siblings like get_mcp_servers and get_trends, though it doesn't explicitly contrast with them.

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?

It gives one concrete usage pattern (pass repo=owner/name to fetch a single repo) and notes the queuing behavior for untracked repos. However, there is no guidance on when to use this versus the other feed/pricing/lookup siblings, and no exclusions or prerequisites beyond the API key note.

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