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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real detail beyond that: the returned code is the page demos with imports rewritten to the CLI install location, which tells the agent the output is runnable rather than raw source. It stops short of saying how many examples are returned or their format.

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?

One dense sentence with the payload (example code, demos, rewritten imports) front-loaded ahead of the usage hint. Nothing is wasted, though the middle clause about CLI imports is slightly compressed and requires a second read.

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?

For a simple read-only lookup with annotations covering safety and no output schema, most of what an agent needs is present. Gaps remain on the undocumented 'type' parameter and on the shape/count of returned examples, which matter for deciding whether a call is sufficient.

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 description coverage is only 50%; 'name' is documented only as 'Item name', and the 'type' enum has no description at all in the schema. The description mentions 'an item' but never explains what 'type' does, whether it is required, or how it changes results, so it fails to compensate for the coverage gap.

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 names a specific resource ('working example code for an item: the demos shown on its page') and a distinctive transformation ('imports pointing where the CLI installs the item'), which separates it from get_item and get_install_command. It does not explicitly contrast itself with those siblings, keeping it below a 5.

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?

'Use it to wire an item up the way it is meant to be used' gives a usage context but no explicit when-not conditions or named alternatives (e.g. get_item for metadata vs this for runnable code). The agent must infer the selection rule from the sibling list.

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