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 states that the tool parses owner and repo, but does not disclose what happens for invalid or non-GitHub URLs, whether it returns parsed values or only validates shape, or whether any input is discarded during processing. This is a significant transparency gap.

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 with no wasted words. It quickly conveys the core purpose without repeating the tool name or padding.

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?

Despite the simple wording, the tool has 9 optional parameters, no annotations, and no output schema. The description does not specify which parameter should contain the GitHub URL, what the parsed owner/repo output looks like, or how errors are handled, so an agent would likely need additional information to invoke it confidently.

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 the baseline is 3. The description adds no parameter-level meaning beyond naming the GitHub URL context, but the schema already documents each parameter, including 'discarded' behavior for several of 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 and resource: 'Parse owner and repo from a GitHub URL.' This clearly distinguishes the tool from sibling shape tools like domain-shape, figma-url-shape, and jira-key-shape, which target different input kinds.

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 the tool should be used when an agent has a GitHub URL and needs owner/repo extracted, but it provides no explicit when-to-use conditions, exclusions, or references to alternative tools such as normalize-url or domain-shape. Usage guidance is left to inference.

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