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

Annotations already declare readOnlyHint and openWorldHint, covering safety and external access. The description adds valuable context beyond that: it says each repo comes with a one-line description and how to fetch raw files, and it warns against live data or transactions. It omits operational details like rate limits or authentication, but these are minor for a public read-only listing.

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?

The purpose and usage trigger are front-loaded, and the paragraph is information-dense with no filler. It is somewhat long because it enumerates repo coverage and return behavior, though each clause is actionable and could be trimmed only slightly.

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 parameters and no output schema, the description carries the missing return information by explaining what each repo entry includes and how to fetch raw files. Combined with annotations for read-only/open-world behavior, it gives the agent everything needed to decide when and how to call it.

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?

There are zero parameters, so the baseline is 4. The description correctly implies no inputs are needed and does not invent parameter semantics.

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?

It states a specific verb and resource: list public Yield.xyz GitHub repos to use as a code reference. It also distinguishes itself from the docs tools and action tools by naming them and explaining what the repos cover.

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 an explicit trigger: use this when stuck on an integration and other docs tools do not provide enough. It also states when not to use it, directing live data and user transactions to the action tools, and names the sibling tools to try first.

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