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

Annotations already cover read-only, idempotent, closed-world semantics, yet the description still adds material facts: results come from a stale snapshot, default page size of 50, full-name ordering, the accountStatus connection indicator, and the authorization requirement. It also warns that repository names are user-defined text, which is useful untrusted-content context.

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 and scope are front-loaded, and every clause carries new information (fields, limit, ordering, query behavior, accountStatus, prerequisites). The middle section is a long run-on sequence, which slightly hurts scannability, but there is no filler.

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 enumerates the returned fields (full name, name, default branch, private flag, accountStatus) and the ordering and page size, which is what an agent needs to plan around the response. Combined with the prerequisite and snapshot caveat, nothing essential is missing for a two-parameter read tool.

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?

With 0% schema description coverage the description must carry the load, and it does: limit is 'at most limit (50 by default)' clarifying the default the schema omits, and query is documented as substring matching on the full name rather than a prefix/exact match. It does not mention the min/max constraints (1, 50, 100 chars), but those are visible in the schema itself.

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 with precise scope: repositories accessible to GitHub installations connected to this Eurobase account, read from the recorded snapshot. It goes further than the title by naming the returned fields and the snapshot source, so an agent knows exactly what it gets.

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?

Gives clear situational context: the data comes from the dashboard snapshot rather than live GitHub, and connection/access are managed by the user in the dashboard, which tells the agent not to attempt remediation here. It also states the grant prerequisite. It stops short of explicitly routing the agent (e.g., 'use before eurobase_create_project'), but no sibling tool offers an alternative source for GitHub repos.

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