qobrix_get_media

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses the return type ('media metadata including URL/path') and the effect of the optional size parameter. However, it does not mention error handling (e.g., not-found behavior), authentication requirements, or any side effects, which leaves some gaps for a read operation.

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 sentences, front-loaded with the main action and resource, followed by targeted parameter guidance. No repetition of schema fields or filler, and every clause contributes actionable 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?

For a simple two-parameter getter with no output schema, the description covers the core purpose, the return value, and the optional parameter semantics. It could mention not-found behavior or clarify the 'Media Lifecycle' context more, but it is sufficiently complete for typical use.

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 the baseline is 3. The description adds practical value by explaining the use of the 'size' parameter with concrete examples ('thumbnail', 'medium', 'large') and describing their intended use cases ('preview grids', 'full-resolution display'), going beyond the schema's generic 'Image size variant'.

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 clearly states the verb ('Get'), resource ('single media item by UUID'), and purpose ('media detail view in the Media Lifecycle'). It distinguishes this from sibling tools like qobrix_list_media by emphasizing 'single' and by specifying the return of metadata including URL/path.

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?

Provides context ('media detail view in the Media Lifecycle') and explicit guidance on when to use each size variant ('thumbnail' for preview grids, 'large' for full-resolution display). It does not explicitly name alternatives or state when not to use, but the 'single' wording implies a contrast with list operations.

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