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 only says 'Parse owner and repo' and does not mention what happens with invalid URLs, whether inputs are discarded, what the return structure looks like, or whether the operation is side-effect free. The schema hints at 'discarded' behavior, but the tool description itself does not.

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 filler. Every word contributes to identifying the tool's purpose and primary input.

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?

The tool has no output schema and no annotations, so the description should explain return values and behavior. It names owner and repo conceptually, but omits the exact return format, invalid-input behavior, and whether the other eight accepted parameters are ignored. This is insufficient for an agent to invoke it confidently in all cases.

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%, so the baseline is 3. The description adds value by identifying that the 'url' parameter is the relevant input and that the outputs are owner and repo, which disambiguates the purpose among nine optional parameters. It does not define exact formats, but the schema already covers parameter-level descriptions.

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.' It clearly distinguishes this tool from sibling shape tools like domain-shape, figma-url-shape, and jira-key-shape by narrowing the scope to GitHub URLs.

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 phrase 'from a GitHub URL' implies the tool should be used when a GitHub repository URL is available and owner/repo extraction is needed. However, it does not explicitly state when not to use it or mention alternatives such as figma-url-shape or jira-key-shape.

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