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 agent knows this is a safe read operation. The description adds that it returns 'preview URL, dimensions, formats, author' and supports bulk execution via 'ids', which is useful. However, it does not disclose any potential limitations (e.g., rate limits, required authentication) or behavior for invalid IDs. With annotations covering the safety profile, a 3 is appropriate.

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 two sentences, front-loaded with the main purpose and key return fields, followed by a note on bulk support. Every sentence earns its place; no fluff or redundancy. It is concise and well-structured.

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?

The tool has 3 parameters, no output schema, and annotations that cover safety. The description explains the return fields and bulk support, which is helpful. However, it does not explain the 'type' parameter or any prerequisites (e.g., authentication via 'authenticate' or 'connect' tools). Given the moderate complexity and lack of output schema, the description is adequate but could be more complete by clarifying the 'type' parameter and any required setup.

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%, so the description must compensate. The description mentions 'ids' for bulk support, which adds meaning to the 'ids' parameter. However, it does not explain the 'id' parameter (though it's required and self-explanatory) or the 'type' parameter (which has an enum of photo/vector/video/icon). The description adds some value for 'ids' but leaves 'type' unexplained, which could be important for filtering or specifying the stock type. Given the low coverage, a 3 is fair.

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 tool's purpose: 'Full details for a single Freepik stock item: preview URL, dimensions, formats, author.' It uses a specific verb ('get') and resource ('stock item'), and lists the key data fields. It distinguishes from siblings like magnific_stock_search and magnific_stock_download by focusing on retrieval of full details for a single item, though it doesn't explicitly name those siblings.

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?

The description implies usage: to fetch full details for a stock item, and mentions bulk support via 'ids'. However, it does not explicitly state when to use this tool versus alternatives like magnific_stock_search (for searching) or magnific_stock_download (for downloading). The context of 'single item' vs 'bulk' is clear, but no explicit exclusions or alternative tool names are provided.

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