Get full details for one repository by UUID.

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that the response includes GPG key, snapshot, and introspection fields, which is useful context, but this return-shape information is also carried by the output schema, so incremental behavioral value is modest.

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?

Three short sentences, front-loaded with purpose before the usage constraint. There is mild redundancy, as 'Call this for one repository only' repeats what the schema already says, but overall it is tight.

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 one-parameter read tool with a full output schema and readOnly annotations, the description covers purpose, sourcing, and return scope. Nothing an agent needs to call it correctly is missing, though it leans on the output schema for return detail.

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 100% and the parameter is self-documenting, but the description adds sourcing guidance ('from list_repositories or from the user') and reinforces the single-repository constraint beyond the raw schema text.

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 (get), resource (repository), scope (one by UUID), and explicitly distinguishes itself from list_repositories. An agent can immediately tell this is the single-item fetch rather than the list operation.

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?

'Call only for a single repository UUID from list_repositories or supplied by the user' gives clear context and points to the sibling that produces the identifier. It doesn't state a when-not condition, but the single-vs-list split is implied well enough.

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