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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only says 'Parse owner and repo from a GitHub URL', which implies a read-only operation but does not explain behavior on invalid URLs, return format/errors, or that this tool performs no network fetch. Some discard behavior is present in input parameter descriptions, not in the tool description itself.

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 one short, front-loaded sentence with no fluff. Every word contributes: the action and the input/output are stated directly.

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 large sibling set of similar URL/shape tools and a seven-property input schema, a single-line description is insufficient. It omits which parameter to supply, what the output shape looks like, and how to handle non-GitHub or malformed URLs. The description is clear in isolation but incomplete for correct invocation in context.

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?

The schema has high per-property description coverage, so the baseline is 3. The description adds that the `url` parameter is intended to be a GitHub URL for owner/repo extraction, but it does not clarify which of the seven disparate parameters are relevant or that irrelevant ones like city, feed, json, and path are ignored in this call. It adds only marginal meaning beyond the 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 states a specific verb ('Parse'), a specific output ('owner and repo'), and a specific input scope ('GitHub URL'), which clearly distinguishes it from siblings like normalize-url, domain-shape, or figma-url-shape. This is a precise purpose statement.

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 gives no direct guidance on when to use this tool versus alternatives. It does not explicitly say to use it when a GitHub owner/repo pair is needed, nor does it exclude non-GitHub or generic URL cases. This is essentially no usage guidance beyond the implied purpose.

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