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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description instead adds genuinely useful entitlement behavior — free items always include source, Pro items only with a valid Pro token. It does not state what happens on a missing slug or an invalid/absent Pro token (error vs. silent omission), which is the main remaining gap.

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?

It is one compact sentence and front-loaded, but 'when to use it and when not' is wasted space that also misleads the reader into expecting selection guidance. The rest is a dense but efficient inventory of returned content.

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 no output schema, the description carries the burden of describing the return payload and does so thoroughly by enumerating each section. For a read tool whose annotations already cover safety, the only notable omission is failure behavior for bad slugs or insufficient entitlement.

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 baseline is 3, but the description adds real meaning about the includeSource lever: source is gated by the item's tier and a valid Pro token, so the parameter is a request rather than a guarantee. That is semantic value the schema ('Include the source files when allowed') only hints at.

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 conveys a specific resource (one item/component) and enumerates exactly what the response bundles: props table, keyboard, accessibility, motion, files, npm dependencies, install command, and source. It stops short of a crisp verb-led statement and never contrasts with siblings like get_source or get_install_command, whose content this tool appears to include, so the agent must infer the overlap.

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 phrase 'when to use it and when not' reads as a description of a field inside the returned docs, not as guidance about when to call this tool versus get_source, get_install_command, or get_skill. No conditions, prerequisites, or alternatives are given for tool selection.

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