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

There are no annotations, so the description carries the full behavioral disclosure burden. It only says 'Parse owner and repo' and does not disclose whether the tool is read-only, whether it validates or fetches the URL, how invalid inputs are handled, or what the return shape is. The 'discarded' behaviors are present only in the schema, not in the tool description.

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 short sentence with no filler, front-loading the action and target. Every word earns its place, and the core purpose is immediately clear.

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?

With nine parameters, no annotations, and no output schema, the one-sentence description is not complete enough. It does not explain the role of the non-URL parameters, whether any are required, or the structure of the returned owner/repo result, leaving the agent to guess key details.

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 value by clarifying that the url parameter is expected to be a GitHub URL and that owner/repo are extracted from it, which the url schema entry does not clearly state. However, it gives no additional meaning for the other eight 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 states a specific verb ('Parse'), a specific resource ('owner and repo'), and a specific input domain ('GitHub URL'). This clearly distinguishes the tool from sibling shape tools such as figma-url-shape and jira-key-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?

The phrase 'from a GitHub URL' gives an implied usage context, but the description provides no explicit when-to-use or when-not-to-use guidance and does not name alternatives like normalize-url or file-path-ok. It is enough for the agent to infer the main use case, but not enough to make confident routing decisions among the many sibling tools.

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