get_repository

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add one useful piece of behavior ('including parent if it's a fork'), but it does not disclose return structure, potential rate limits, or any other execution traits. This is a minor value-add over the tool name.

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?

The description is a single, front-loaded sentence that directly states the action and the key extra behavior (parent if fork). No words are wasted, and it is perfectly scannable for an agent.

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 simple read-only repository fetch with only two obvious parameters and no output schema, the description is minimally viable. However, it omits parameter semantics and any hint of the return shape, leaving some ambiguity about what 'detailed information' means. It is adequate but not thorough, especially given the wide array of sibling tools.

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 0%, so the description must compensate for the lack of parameter documentation. It does not: it merely says 'specific repository' without explaining that 'owner' and 'repo' are required string parameters or how they combine to identify the repository. The parameter names are self-explanatory, but the description adds no semantics beyond them.

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 uses a specific verb ('Get') and resource ('detailed information about a specific repository'), clearly indicating the tool's function. It also distinguishes itself from sibling tools by including the parent fork context, which is unique and not obvious from the tool name alone.

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?

The description implies when to use the tool (when detailed repository information is needed) but provides no explicit guidance about when not to use it or which sibling tools to prefer as alternatives. The context is clear enough for an agent to infer basic usage, but it lacks exclusions or comparisons.

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