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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a genuinely non-obvious trait: the item URL is withheld when the farm's tier is below item.minTier (default Silver) and an upgrade message is returned instead. That conditional output behavior is exactly the kind of context structured fields do not carry.

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?

Two short sentences with no filler; the core operation is stated first and the conditional gating caveat immediately follows. Every clause carries information.

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, so the description usefully flags the one return-value variant an agent must anticipate (omitted URL plus upgrade message). It leaves the rest of the item payload and the error case of an unknown itemId unaddressed, but for a 2-param read tool with covering annotations this is nearly 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 0% for both required parameters, so the description must compensate and largely does not: it never explains what farmId or itemId are or their format. The reference to "farm tier" and "item.minTier" only obliquely suggests that farmId selects the tier used for the gating check.

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 uses a specific verb+resource ("Get one Library item") and the singular "one" implicitly contrasts with the sibling list_library_items. It is clear what it does, but it never names the sibling or states that it requires an existing itemId.

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?

There is no statement of when to use this tool versus list_library_items or other get_* tools, and no prerequisite guidance beyond the schema's required fields. The tier-gating sentence describes output behavior, not when-to-use.

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