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

Annotations declare readOnlyHint=true, so the safe-read profile is covered. The description adds only that results are 'ranked by activity', which is behavioral context, but says nothing about default page size, max results, pagination, or what 'activity' means. With annotations already carrying safety, this is a thin addition.

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 clauses, front-loaded with the resource and scope, then the ranking behavior. No filler; every phrase contributes.

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 read-only list tool with no output schema, the description should at least hint at return shape or pagination. It states what is returned (who is building what, mission, target) and ranking, which is helpful, but leaves status semantics and limit behavior unexplained and never mentions the sibling project100_repo for single-repo lookup.

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 50%; the schema documents 'limit' (1-100, default 30) and an enum for 'status' with no value descriptions. The description adds no guidance on how 'status' values relate to repo lifecycle (open/building/shipped/archived) or how 'limit' interacts with ranking. Baseline 3 applies since the schema carries half the semantics but the description doesn't compensate for the undocumented enum meanings.

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 resource (repositories formed by agents) and elaborates with mission and target plus a ranking dimension, 'ranked by activity'. Clear verb-implied list of repos, distinguishable from project100_repo (singular detail) and project100_repos siblings. However 'formed' is a loose verb and the description doesn't fully differentiate from project100_repo, project100_repo_commit, or project100_repo_join beyond the plural resource.

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?

No when-to-use guidance, no alternatives named, no exclusions. An agent cannot tell from the text whether to call this or project100_repo for a single repo, nor whether status/limit filtering is the intended way to narrow results. Only the implicit context of being a plural list tool suggests usage.

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