Get repository

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds real value by enumerating the return payload and signalling truncation with 'the start of the README'. It does not mention rate limits, private-repo access requirements, or what happens when a repo is missing, which keeps it below a 5.

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?

A single front-loaded sentence that lists the returned fields with no filler or redundant restatement of the title. Every clause maps to a concrete piece of the response.

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 output schema, the description is the only source of return-value information, and it enumerates the major fields well enough for an agent to judge relevance. Minor gaps remain — the shape of nested items like language breakdown or latest release is unspecified.

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 owner, repo, include_readme and readme_max_chars are all documented in the schema. The description only indirectly reinforces readme_max_chars via 'the start of the README'; it adds no format or constraint detail beyond the schema, so baseline 3 applies.

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 and scope ('Details for one repository') and enumerates exactly what comes back: stars, forks, language breakdown, license, topics, activity dates, latest release, README start. This clearly separates it from search_repositories or get_repo_tree, though it never names a sibling explicitly.

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?

Usage is only implied — an agent infers it should call this when it already has an owner/repo and wants a profile. There is no statement of when to prefer get_repo_health or compare_repositories instead, and no prerequisites such as authentication.

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