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

With no annotations provided, the description carries full burden. It discloses the operation type (copy) and mentions failure cases ('Raises: Exception'), but doesn't cover permissions needed, rate limits, or what happens with existing destination files. It adds some context but lacks comprehensive behavioral details.

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 well-structured with clear sections (Args, Returns, Raises), front-loaded purpose statement, and no wasted sentences. Each part earns its place by providing essential information efficiently.

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 2 parameters with 0% schema coverage and no output schema, the description does well by fully explaining parameters and return format. However, as a mutation tool with no annotations, it could better cover behavioral aspects like idempotency or error specifics for completeness.

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. It fully explains both parameters: 'volume_name' as the Modal volume name, and 'paths' with detailed semantics including source/destination roles and an example. This adds significant value beyond the bare schema.

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 ('Copy files') and resource ('within a Modal volume'), specifying it can copy single files or multiple files to directories. It distinguishes from siblings like 'get_modal_volume_file' (read) and 'put_modal_volume_file' (upload).

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 for copying files within a Modal volume, but doesn't explicitly state when to use this vs. alternatives like 'put_modal_volume_file' for uploading external files or 'remove_modal_volume_file' for deletion. It provides clear context but lacks explicit exclusions.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that deployment can fail and raises exceptions, but doesn't describe what 'deploy' actually does (e.g., creates resources, starts services), what permissions are required, whether it's idempotent, or any rate limits. For a deployment tool with zero annotation coverage, this is insufficient.

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 appropriately sized with clear sections (Args, Returns, Raises). It's front-loaded with the core purpose statement. However, the 'Raises' section could be more specific than just 'Exception'.

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 deployment tool with no annotations, no output schema, and minimal parameter documentation, the description is incomplete. It doesn't explain what deployment entails, what the return dictionary contains, or provide sufficient context for safe and effective use. The sibling tools suggest this operates in a Modal environment, but that context isn't leveraged.

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. It adds that the parameter is 'The absolute path to the Modal application to deploy' which provides basic semantics, but doesn't explain what constitutes a 'Modal application' (e.g., a directory, a specific file format), path format requirements, or validation rules. This provides minimal compensation for the schema gap.

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 states the tool 'Deploy a Modal application' which provides a clear verb+resource combination. However, it doesn't differentiate from sibling tools (which all deal with Modal volumes/files, not deployments), making the purpose clear but lacking sibling differentiation.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites, when deployment is appropriate, or what alternatives might exist for similar operations.

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

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it's a download operation (implies read-only but not explicitly stated), can overwrite files with 'force', supports stdout output, and may raise exceptions on failure. However, it doesn't mention rate limits, authentication needs, or detailed error handling beyond generic exceptions.

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 well-structured and front-loaded with the core purpose. Each sentence earns its place: the opening statement sets context, the Args section details parameters efficiently, and the Returns/Raises sections provide necessary completion info without redundancy. No wasted words.

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 no annotations and no output schema, the description does a good job covering the tool's complexity. It explains parameters thoroughly, hints at behavior (overwrite, stdout), and mentions error handling. However, it could be more complete by explicitly stating read-only nature or contrasting with upload/list siblings more directly.

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 fully. It provides detailed semantics for all 4 parameters: explains what 'volume_name' and 'remote_path' are, clarifies 'local_destination' defaults and special case ('-'), and defines 'force' behavior. This adds significant value beyond the bare schema.

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 specific action ('Download files from a Modal volume') and distinguishes it from siblings like 'list_modal_volume_contents' (which lists contents) and 'put_modal_volume_file' (which uploads). It specifies the resource (Modal volume) and verb (download) precisely.

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 context by mentioning downloading from a volume, but does not explicitly state when to use this tool versus alternatives like 'copy_modal_volume_files' or 'list_modal_volume_contents'. It provides clear parameter defaults and behavior hints (e.g., using '-' for stdout), but lacks explicit sibling differentiation.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the return format ('A dictionary containing the parsed JSON output'), which adds some value, but fails to address critical aspects like read-only nature, error conditions, pagination, or rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 well-structured and concise, with a clear purpose statement followed by separate 'Args' and 'Returns' sections. Each sentence adds value without redundancy, making it easy to parse and understand quickly. The formatting enhances readability without unnecessary verbosity.

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 the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and parameters but lacks usage guidelines, behavioral details, and output specifics. While it meets a minimum viable standard, it doesn't fully equip an agent for optimal tool selection and invocation in context with 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?

The description adds meaningful context for both parameters: 'volume_name' is explained as 'Name of the Modal volume to list contents from,' and 'path' as 'Path within the volume to list contents from. Defaults to root ("/").' This compensates for the 0% schema description coverage by clarifying the purpose and default value, though it doesn't detail constraints or examples.

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: 'List files and directories in a Modal volume.' It specifies the verb ('List') and resource ('files and directories in a Modal volume'), making the action and target explicit. However, it does not differentiate this tool from its sibling 'list_modal_volumes', which might cause confusion without additional context.

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 provides no guidance on when to use this tool versus alternatives. It lacks context such as prerequisites, when to choose this over 'list_modal_volumes' (which lists volumes themselves), or how it relates to other siblings like 'get_modal_volume_file'. This absence of usage instructions leaves the agent without clear direction.

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

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions JSON output format but lacks critical details: whether this requires authentication, has rate limits, returns paginated results, or what happens on errors. For a list operation with zero annotation coverage, this leaves significant behavioral gaps.

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 appropriately concise with two focused sentences. The first sentence states the core action and implementation, while the second describes the return format. There's no wasted text, though it could be slightly more structured with clearer separation of concerns.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description provides adequate but minimal context. It covers what the tool does and the return format, but lacks behavioral details that would be helpful for an agent. For a read-only list operation, this is minimally viable but leaves room for improvement.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the empty parameter set. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose and output. This meets the baseline expectation for parameterless tools.

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 ('List') and resource ('Modal volumes') with specific implementation details ('using the Modal CLI with JSON output'). It distinguishes from siblings like 'list_modal_volume_contents' by focusing on volumes themselves rather than contents. However, it doesn't explicitly contrast with other volume-related tools like 'copy_modal_volume_files'.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or compare it to sibling tools like 'list_modal_volume_contents' for different use cases. The agent receives no usage direction beyond the basic function.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the upload operation, overwrite behavior via the 'force' parameter, and error handling ('Raises: Exception'), but doesn't cover aspects like authentication requirements, rate limits, or what specific data the return dictionary contains.

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 well-structured with clear sections (Args, Returns, Raises) and front-loaded purpose statement. It's appropriately sized for a 4-parameter tool, though the 'Raises' section could be more specific than 'Exception' to be fully optimal.

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 no annotations and no output schema, the description provides adequate coverage for core functionality but has gaps. It explains parameters well and mentions return type (dictionary) and error handling, but doesn't detail the dictionary structure or other behavioral aspects like side effects or prerequisites, leaving some context incomplete.

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 adds significant semantic value beyond the input schema, which has 0% description coverage. It explains all four parameters clearly: volume_name identifies the target, local_path specifies the source, remote_path defines the destination with default and directory-handling rules, and force controls overwrite behavior. This fully compensates for the schema's lack of 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?

The description clearly states the specific action ('Upload a file or directory') and target resource ('to a Modal volume'), distinguishing it from sibling tools like get_modal_volume_file (download) or remove_modal_volume_file (delete). It uses precise terminology that matches the tool name without being tautological.

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 for uploading files to Modal volumes but doesn't explicitly state when to use this tool versus alternatives like copy_modal_volume_files or when not to use it (e.g., for downloading). It provides some context through parameter explanations but lacks explicit guidance on tool selection.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool performs a delete operation and mentions potential failure ('Raises: Exception: If the delete operation fails for any reason'), which is useful. However, it lacks details on permissions required, whether deletions are permanent or reversible, rate limits, or what the result dictionary contains. For a destructive tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 appropriately sized and well-structured. It starts with a clear purpose statement, followed by organized sections for 'Args', 'Returns', and 'Raises'. Each sentence adds value without redundancy, making it easy to scan and understand. The formatting enhances readability without unnecessary verbosity.

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 the tool's complexity (destructive operation with 3 parameters), no annotations, and no output schema, the description is moderately complete. It covers the basic purpose and parameters but lacks details on behavioral aspects like safety warnings, output structure, or error handling specifics. For a delete tool, more context on irreversible actions or confirmation steps would improve completeness, but it meets minimum viable standards.

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 adds meaningful semantics beyond the input schema, which has 0% description coverage. It explains each parameter: 'volume_name' as 'Name of the Modal volume to delete from', 'remote_path' as 'Path to the file or directory to delete', and 'recursive' with specific usage context ('If True, delete directories recursively. Required for deleting directories'). This compensates well for the schema's lack of descriptions, though it doesn't cover all potential edge cases.

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: 'Delete a file or directory from a Modal volume.' It specifies the verb ('Delete') and resource ('file or directory from a Modal volume'), distinguishing it from siblings like 'copy_modal_volume_files' or 'get_modal_volume_file'. However, it doesn't explicitly differentiate from other destructive operations like 'deploy_modal_app' beyond the resource scope.

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 context through the 'recursive' parameter explanation ('Required for deleting directories'), suggesting when to set this flag. It doesn't provide explicit guidance on when to use this tool versus alternatives like 'list_modal_volume_contents' for checking before deletion or mention any prerequisites. The guidance is functional but not comprehensive.

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