List Row Attachments

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the tool is clearly read-only and idempotent. The description adds that it returns 'Array of attachment metadata', but does not disclose any additional behavioral traits beyond what annotations provide. No contradiction.

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 extremely concise: three lines cover purpose and argument details in a clear, bullet-like format with no redundant information. Every sentence adds value.

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 simple list tool with two required parameters and no output schema, the description is mostly complete. It states the function and arguments, and annotations cover safety. However, it could mention potential empty results or access requirements for higher 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 coverage is 0% (no parameter descriptions in schema), so the description carries the full burden. It adds 'Target sheet ID' and 'Target row ID', clarifying the parameters' roles, but provides no additional meaning beyond the basic type and requirement already in the 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 'List all attachments on a specific row' with a specific verb and resource, distinguishing it from sibling tools like 'smartsheet_list_attachments' (which likely lists all attachments in a sheet) and 'smartsheet_attach_url_to_row'.

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 does not explicitly guide when to use this tool versus alternatives such as 'smartsheet_list_attachments' or 'smartsheet_search'. It relies on the agent inferring context from the tool name and sibling list, with no explicit exclusions or prerequisites mentioned.

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