Get one library item

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the raw endpoint path; it says nothing about what a fetched item contains, whether missing ids error, or how this differs from the content/file variants.

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 front-loaded sentence with the endpoint in parentheses — no wasted words. It is efficient but borders on under-specified rather than merely concise.

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 one-parameter read with readOnly annotations, little explanation is strictly required. However, with no output schema and three sibling tools in the same namespace, the description should at least indicate what an item record is versus a file/content fetch.

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 0%, so the single required `id` is undocumented. The path template `{id}` implies it is the library item identifier, which is a small gain, but nothing states the expected format (numeric, UUID) or where an agent obtains a valid id.

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 gives a specific verb and resource ("Get one library item") plus the underlying endpoint, so an agent knows exactly what is fetched. It does not distinguish this from close siblings like creativeLibrary_content or creativeLibrary_file, which likely return the asset itself rather than an item record.

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 guidance on when to use this versus creativeLibrary_list (browse many) or creativeLibrary_content/file (retrieve the asset). The agent must infer the choice from names alone.

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