tokportal_upload_image_from_url

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

Annotations already set readOnlyHint=false, idempotentHint=false, and destructiveHint=false, indicating a non-read, non-idempotent, non-destructive mutation. The description confirms it's a write operation ('stores it permanently'). However, it doesn't clarify whether the same URL can be imported multiple times (dedup behavior), what happens on fetch failure, whether the tool blocks or returns errors for non-image URLs, or any rate limits. With annotations providing baseline safety info, a 3 is appropriate—adds some context but doesn't fully disclose side effects.

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 consists of two concise sentences: the first states the purpose, the second elaborates on the mechanism and outcome. Every word is informative with no filler. Front-loaded with verb and resource. Perfectly sized for quick comprehension.

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 2 parameters with full schema coverage, clear annotations, and a straightforward purpose. The description explains the core behavior (fetch then store) and parameter expectations (public direct image URL). With no output schema, the description doesn't detail return values (e.g., uploaded image ID or URL), which is a minor gap. However, given the tool's simplicity and the richness of sibling context, the description is nearly complete. A 4 reflects the minor output documentation gap.

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 100%, so baseline is 3. The description adds value by implying that the 'url' parameter must be a 'public direct image URL', emphasizing accessibility and format. 'purpose' has enum values in schema but description doesn't elaborate; however, for a 2-param tool with comprehensive schema documentation, the description's added context (especially around URL) merits an above-baseline score.

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 'Import an image from URL' with specific verb 'Import' and resource 'image'. It explicitly distinguishes itself by sourcing from a URL ('Fetches a public direct image URL'), contrasting with siblings like 'tokportal_upload_image' (likely from local file) and 'tokportal_upload_image_direct' (different method). This makes the purpose unambiguous and distinct.

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 implicitly communicates when to use: when you have a public direct image URL to fetch into TokPortal storage. The sibling names 'tokportal_upload_image' and 'tokportal_upload_image_direct' provide alternatives for other sources/methods, but no explicit when-not-to use guidance or prerequisites (e.g., image format restrictions, size limits, URL accessibility checks). Clear context but lacks exclusions.

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