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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the parse action but does not disclose what happens with invalid URLs, whether it returns owner/repo or a boolean shape check, error behavior, or side effects. The name 'shape' implies validation but the description does not confirm that, leaving the agent uncertain about the output and edge cases.

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 concise sentence with no fluff, which is good for brevity. However, given the mismatch between the description and the large schema, it is under-specified and does not provide necessary context. It is concise but not well-structured to convey essential information about parameter usage.

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?

This tool has 9 optional parameters, no output schema, and no annotations, yet the description is just one line. It fails to explain the output format, how to specify the GitHub URL among the many parameters, error handling, or any constraints. The description is grossly inadequate for an agent to invoke the tool 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?

Although schema coverage is 100%, the description does not connect any parameter to the function. It says 'parse owner and repo from a GitHub URL' but never indicates that the 'url' parameter is the relevant one. The schema lists nine unrelated parameters, and without clarification, an agent cannot know which to populate. The description adds no value beyond the schema and actually obscures the intended input.

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', which is specific and distinguishes it from siblings like domain-shape or figma-url-shape. However, the schema includes many unrelated parameters (city, feed, host, etc.), so the description's narrow scope does not fully clarify that this tool likely also performs shape checks on those inputs, leaving some ambiguity about its actual coverage.

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 does not mention any conditions, exclusions, or reference to sibling shape tools. An agent has no information about when github-repo-shape is preferred over domain-shape or jira-key-shape.

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