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

No annotations are provided, so the description must disclose behavior. It only mentions parsing owner and repo, but does not describe return format, error handling, or the fact that many schema parameters are ignored. The schema includes fields like 'city' and 'feed' which are unrelated to the stated purpose, and the description does not clarify this discrepancy.

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 sentence with no waste, but it is under-specified for a tool with nine parameters and no output schema. It lacks structure that would help an agent understand the tool's full scope.

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 tool with nine parameters, no annotations, and no output schema, this description is severely incomplete. It does not explain what the tool returns, how the parameters relate, or how it handles invalid inputs, leaving an agent unable to call it correctly.

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 description does not reference any of the nine parameters, so it adds no meaning beyond the schema. With 100% schema coverage, a baseline of 3 is warranted, but the description fails to clarify which parameter corresponds to the GitHub URL or what the other parameters are for, making it less helpful than the schema alone.

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 verb 'parse' and the resource 'owner and repo from a GitHub URL', making the primary purpose unambiguous. It also distinguishes itself from siblings like figma-url-shape and domain-shape by specifying GitHub repos.

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 provides no guidance on when to use this tool versus alternatives. It simply states the function without mentioning conditions, prerequisites, or comparisons to other shape tools.

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