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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly implies a read-only parse and names the extracted values, but it does not describe behavior for invalid or non-GitHub URLs, whether other supplied fields are ignored, or what the return shape looks like. For a pure parse tool, this is a moderate gap rather than a severe one.

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 and no repetition of schema information. Every word contributes to the core meaning.

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?

For a narrow parse tool, the description plus the schema is minimally viable: an agent can infer that it should pass a GitHub URL. However, with no output schema and no annotations, the description omits the return contract and invalid-input behavior, which leaves some uncertainty for an agent choosing and invoking the tool.

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 already documents all parameters (100% coverage), so the baseline is 3. The description adds the useful constraint that the URL should be a GitHub URL and that owner/repo are the intended outputs, but it does not clarify which of the many optional parameters to provide or that most are discarded.

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 clearly states the tool's action ('Parse'), the resource being parsed ('owner and repo'), and the input scope ('from a GitHub URL'). It is unambiguous and can be distinguished from sibling shape tools like figma-url-shape or jira-key-shape without opening the schema.

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 when-to-use or when-not-to-use guidance. It does not mention alternatives such as normalize-url or browser-url-ok, nor does it clarify the condition that should lead an agent to select this tool over others.

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