get_repository

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds nothing beyond that: no note on permission requirements, 404 behavior for unknown ids, or what the returned repository object contains.

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 short fragments with zero padding and the resource named up front, so nothing is wasted. However, the brevity is under-specification rather than economy — the second sentence only repeats the identity of the tool in URL form.

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 should say what a repository record contains and whether lookups fail loudly on missing ids. Neither is present, and there is no indication of relationship to the many repository sub-resources in the sibling list.

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 carry parameter meaning. The URL template at least implies both ids are path-scoped identifiers, but it never clarifies that project_id must be the owning project or what happens if repository_id belongs to a different project.

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?

"Get repository" restates the tool name, and the GET path restates the same fact in REST form. It does tell an agent this fetches a single repository scoped by project and repository id, but it never distinguishes itself from close siblings like list_repositories, get_repository_references, or get_repository_branches.

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 when-to-use guidance, no mention of prerequisites (e.g. project membership), and no routing to alternatives such as list_repositories for browsing or get_repository_references for dependency info. The agent must infer all selection logic from the name alone.

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