List a record's attachments

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

Annotations already declare readOnlyHint and openWorldHint=false, yet the description adds substantive behavior: content is never read, results span two storage locations, ordering is newest-first, and downloadUrl is only usable inside the user's signed-in Creatio browser session. That last point is exactly the kind of constraint an agent would otherwise get wrong.

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?

Front-loaded with the purpose, then the return shape, then the one critical caveat about downloadUrl. Dense but every sentence carries information the agent needs; no filler.

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?

No output schema exists, and the description compensates by spelling out the response envelope including files array fields, kind variants, optional url/downloadUrl, and hasMore. Combined with the auth-session caveat, an agent has everything needed to call and interpret this correctly.

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 id, entity, and top are already documented with examples and bounds. The description adds only the implicit 'one record' scoping and 'newest first' ordering; it says nothing extra about entity naming or top limits. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Files and links attached to one record') and even names the two backing stores it aggregates (the object's <Entity>File table and SysFile). This is clearly distinguishable from the generic siblings 'read', 'query-sys-settings', and 'get-record-url'.

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?

Gives real operational guidance: metadata only, newest first, and an explicit instruction about downloadUrl ('give it to the user, you cannot fetch it'), which prevents a failed tool call. It does not name a sibling alternative or state when not to use it, so it stops short of a 5.

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