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

No annotations are present, and the description gives no indication of side effects, permissions, or internal behavior. The phrase 'Path discarded' is unclear and does not explain what the tool actually does with the URL.

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 only one sentence and lacks any structured detail. While concise, it omits essential information about the tool's function, input expectations, or output format.

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?

There is no output schema, no examples, and no explanation of what 'shape' refers to. The tool is poorly defined, making it impossible for an agent to know what to expect or how to interpret the result.

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 are generic and appear auto-generated (e.g., 'HTTPS URL to normalize or cite', 'City name for a public weather hint') and are not tailored to the tool's supposed purpose of parsing Figma URLs. Several parameters (city, feed, zone) are wholly irrelevant, adding confusion rather than meaning.

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 'Parse a Figma file URL. Path discarded.' is vague about what 'shape' means and what output is produced. It does not clearly distinguish from sibling tools like normalize-url or fetch-status, which also deal with URLs.

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. There is no context about scenarios where this tool is appropriate or how it differs from similar tools.

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