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

The description discloses key behavior: it can save to a folder (mutation) and is rate-limited. Annotations (readOnlyHint=false, destructiveHint=false) align with this, but side effects beyond saving are not elaborated.

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 concise and free of fluff, conveying the core purpose and key usage variations in three short sentences.

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 description covers main functionality but lacks details on error cases, exact return format, and the meaning of 'type'. Given the absence of an output schema, some information is missing for complete understanding.

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?

The description explains 'folder_reference' (for saving) and 'ids' (for bulk), but 'type' is not explained, and 'id' is obvious. Parameter coverage is partial; schema descriptions are absent.

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 primary function: returning a signed download URL for a stock item. It also distinguishes from related tools like magnific_stock_get and magnific_stock_search by focusing on download/save functionality.

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?

Usage is implied (for downloading stock items), and bulk support via 'ids' is mentioned. However, there is no explicit guidance on when to use this tool over alternatives or when not to use it.

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