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

No annotations are provided and the description does not mention side effects, permissions, or return format. It is unclear whether the tool performs network calls or purely local parsing.

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 with no redundant text. However, it is perhaps too terse, omitting essential details while maintaining brevity.

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 9 optional parameters and no output schema, the description provides insufficient context to understand the tool's full behavior. It does not explain what 'shape' means, what the output looks like, or how parameters relate to the operation.

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 parameter descriptions seem unrelated to the tool's purpose (e.g., 'city' for weather, 'ref' for git), suggesting a template mismatch. It is unclear which parameters are actually used or what role each plays in parsing the Figma URL.

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 it parses a Figma file URL and discards the path, which is a specific action. However, the meaning of 'shape' is not defined, so it's not fully clear.

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 on when to use this over other URL-related tools like normalize-url or domain-shape. The description provides no context for selection among siblings.

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