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

No annotations are provided, so the description carries the full behavioral disclosure burden. 'Parse' implies a read-only transformation, but the description says nothing about return order, error behavior, or that the schema contains many unrelated optional params whose values are discarded during the shape check.

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 concise, front-loaded sentence with no padding. Every word is relevant; there is no filler or redundant restating of the tool name.

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?

Given the lack of annotations and output schema, plus nine optional parameters with only one clearly relevant to the stated purpose, this description is under-specified. An agent cannot tell which parameters are relevant, what the result looks like, or why the other parameters appear.

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 only limited meaning by indicating that 'url' should be a GitHub URL, which differs from the schema's generic 'HTTPS URL'. It does not help make sense of the other eight schema parameters.

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 action and resource: 'Parse owner and repo from a GitHub URL.' This clearly distinguishes the tool from siblings like jira-key-shape, figma-url-shape, and domain-shape, which target other URL/expression 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?

No explicit guidance about when to choose this tool over alternatives is provided. The sentence implies the use case (having a GitHub URL and needing owner/repo), but it does not state any exclusions or explain the relationship to sibling shape tools.

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