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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds what the tool returns (简介、主要语言、Star 数、Fork 数、链接) and how matching/sorting work, which is useful beyond annotations, though it omits rate limits or pagination beyond per_page.

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?

Purpose is front-loaded, followed by usage guidance and an example. The example duplicates the schema's example, which is minor redundancy but not harmful.

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?

No output schema exists, so the description helpfully lists return fields (简介、语言、Star、Fork、链接). Parameters are fully covered by the schema. Complete enough for correct invocation, though pagination limits beyond per_page are not discussed.

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%, so all parameters are documented in the schema. The description only reiterates sorting by Star/更新时间 and shows the same example as the schema, adding little new parameter meaning.

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?

States a specific verb (搜索) and resource (GitHub 开源仓库), and specifies matching scope (名称/描述/语言) and sort options. An agent can distinguish it easily from siblings like stackoverflow_search or hacker_news_search.

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 says when to use it: tasks involving finding open-source projects, codebases, frameworks, or comparing library popularity. It does not name exclusions or alternatives among siblings, which keeps it from a 5.

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