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

No annotations are provided, so the description carries the full burden for side effects and access behavior. It only says 'Parse', which suggests a local read-only operation, but it never confirms that no network request is made, whether auth is needed, or what happens for malformed URLs. The parameter descriptions about 'discarded' hint at side-effect-free behavior, but the tool description itself does not disclose this.

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, tight sentence beginning with an action verb and no filler. It is well structured and 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?

Given 9 optional parameters, no output schema, and no annotations, the one-sentence description is not enough to determine the required inputs or return format. It does not specify which parameter(s) to supply, how the returned owner and repo are represented, or whether enterprise GitHub URLs are supported. This leaves significant gaps for an agent to resolve.

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?

Although every parameter has a schema description, those descriptions are largely unrelated to the stated purpose: city, feed, json, path, zone, and query appear to belong to other tools and are labeled as discarded. Only url is plausibly relevant, but its schema description says 'HTTPS URL to normalize or cite' rather than 'GitHub URL to parse for owner/repo'. The tool description also fails to indicate which of the 9 optional parameters are actually used.

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 ('Parse') and a clear resource ('owner and repo from a GitHub URL'), which distinguishes it from sibling URL tools like normalize-url or domain-shape. It is immediately understandable what the tool is for, though it does not state the output shape.

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 provides only an implied usage scenario: when a GitHub URL is at hand and owner/repo need extraction. It does not explicitly state when to prefer this over related tools such as normalize-url or jira-key-shape, nor any exclusions. Thus the guidance is present but implicit.

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