get_library_metadata_by_id_on_deck

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. However, the description adds no behavioral context beyond repeating the HTTP path; it never explains what 'On Deck' returns or how it behaves. No contradiction with annotations, but also no added transparency.

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 short and contains no filler, but the first sentence is essentially a tautology and the HTTP path repeats the tool name. It could be restructured to offer meaningful information in the same space.

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 an output schema present, return values do not need to be described, but the core concept 'On Deck' is undefined. The agent has no way to know what this endpoint does, how it differs from the section-level on-deck endpoint, or what kind of item id is expected. This is incomplete for a tool with numerous similarly-named siblings.

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%, and the description provides the only semantic for the 'id' parameter: 'The unique identifier of the item.' This is minimally adequate, though 'item' is vague and does not clarify whether it refers to a library item, metadata entry, or media object.

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 'Get Metadata On Deck' essentially restates the tool name without explaining what 'On Deck' means or what the operation actually does. It does not distinguish itself from the many sibling tools that query metadata by id (e.g., children, reviews, similar), leaving the agent to infer its purpose from the HTTP path alone.

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 about when to use this tool versus alternatives like get_library_sections_by_section_id_on_deck or other get_library_metadata_by_id_* variants. There is no mention of context, prerequisites, or selection criteria.

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