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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description's only added value is enumerating the returned fields (description, status, highlights, tech, links), which is genuinely useful given there is no output schema, but it says nothing about ordering, volume, or whether all projects are returned.

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?

It is short and front-loads the resource, but it is a sentence fragment rather than a complete statement, and the field list competes with any explanation of behavior. Nothing is wasted, but little is delivered for the space used.

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 low-complexity, single-optional-parameter read tool with full annotation coverage, the description is minimally adequate: it conveys the resource and its fields. It omits the existence of category filtering and result scope, which an agent would need to call it optimally, but the schema and annotations cover much of that gap.

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 single optional 'category' parameter is fully documented in the schema, including its five allowed values, so schema coverage is 100% and the baseline applies. The description does not acknowledge that filtering exists at all, so it adds no meaning beyond the schema.

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 is a noun phrase ('Open-source projects with description, status, highlights, tech and links') that implies a read of project records and names the fields each record carries. It never states a verb like 'list' or clarifies scope (all projects? open ones only?), and it does nothing to separate it from siblings such as list_publications or list_posts.

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 statement of when to use this tool versus the other list_* or search tools, and no mention that results can be narrowed by category. An agent must infer the use case entirely from the tool name.

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