download_section_image

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

No annotations provided, but the description discloses the main behavior: downloading a JPEG to a local path with support for downsampling, quality, and partial extraction. It does not detail file overwrite behavior or network usage, but the action is straightforward.

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, concise and front-loaded with the primary action. Every sentence adds value without redundancy.

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?

Given 9 parameters and no output schema, the description covers the main purpose and customization options. It could mention that the file is saved to filePath (default provided in schema) but is adequate for an agent to understand the tool's role among diverse 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?

Schemas provide 100% coverage of parameter descriptions. The description adds high-level context by explaining the purpose of downsample, quality, and region parameters (top, left, width, height) beyond the schema's technical descriptions.

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?

Description clearly states the tool downloads a 2D section image as JPEG to a local path, listing key features (downsampling, quality, partial region). It distinguishes from siblings like download_atlas_image by specifying the image type and format.

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?

Description implies usage for downloading section images with optional features but does not provide explicit guidance on when to use this tool versus alternatives (e.g., download_atlas_image). No 'when not to use' or exclusion criteria.

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