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 only states the core action but fails to explain that only the 'url' parameter is actually used while others are discarded, nor does it describe error behavior, output format, or any side effects. The schema's generic parameter descriptions (e.g., 'URL to normalize or cite') do not clarify the GitHub-specific behavior, creating ambiguity about how the tool behaves with other parameters.

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 extremely concise (one sentence) and front-loaded with the purpose. However, conciseness comes at the cost of necessary details given the tool's complexity (9 parameters, no annotations). It lacks structure to guide an agent on which parameters matter, making it under-specified rather than efficiently concise.

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?

The description is grossly incomplete for a tool with 9 parameters and no output schema or annotations. It does not explain which parameter is the input, what the output looks like, how it handles invalid URLs, or why the other parameters are present. An agent cannot confidently invoke this tool correctly based solely on the description and schema.

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 coverage is 100%, so each parameter is described in the schema. However, the tool description does not map its purpose to specific parameters; it implicitly suggests 'url' is relevant but doesn't clarify the roles of the other 8 parameters. The description adds minimal meaning beyond the schema, so baseline 3 is appropriate.

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 action (parse) and resource (owner and repo from a GitHub URL). It distinguishes itself from siblings like domain-shape or figma-url-shape by specifying GitHub, so an agent can infer its primary use. However, it omits mention of validation or 'shape' checking implied by the name, which slightly reduces clarity.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't state conditions like 'Use this when given a GitHub URL' or mention that other shape tools handle different URL types. The description offers no exclusions or context for selection.

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