get_repository

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds one behavioral detail—workspace is resolved via 'standard precedence'—but leaves that precedence undefined and offers no further behavior or side-effect 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?

One compact sentence conveys the core action, the required parameter, and the workspace-resolution behavior with no filler or repetition of annotation values. The information is well front-loaded.

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 annotated read-only getter, this is mostly adequate, but the undefined 'standard precedence' is a genuine gap for an AI agent choosing and invoking the tool. With no output schema and no return-format guidance, the description could usefully clarify what 'details' includes.

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 the parameter-explanation burden. It clarifies that 'repo' is required and 'workspace' is resolved, but it does not define valid formats, the meaning of 'standard precedence', or how the two parameters interact. This is insufficient compensation for an undocumented schema.

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 ('Returns') and identifies the resource ('details for a specific repository'), clearly distinguishing it from sibling list_repositories. The scope is unambiguous: this is a single-repository read 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?

It states a prerequisite ('Requires repo') and hints at workspace resolution, but it never explicitly says when to prefer this tool over list_repositories or how the precedence relates to other workspace-related siblings. Usage context is implied rather than made explicit.

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