slide_get_agent_file_versions

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

With no annotations, the description carries the full burden. 'Get' conveys a read-only operation, and 'snapshot versions available' indicates the kind of data returned. However, it says nothing about pagination behavior, output shape, or error conditions, leaving some behavioral ambiguity for a no-annotation tool.

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 a single front-loaded sentence with no filler. Every word contributes to identifying the tool's purpose and scope.

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 read-only getter with a fully documented schema, the statement is minimally adequate. But with no output schema and no annotation, it doesn't describe return values, pagination, or how this differs from sibling tools, so the context is not fully complete.

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 the schema already documents all six parameters. The description only reinforces the roles of agent_id and path by mentioning 'specific file path on an agent'; it adds no meaning beyond the schema, which earns the baseline 3.

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 names a precise verb ('Get'), a specific resource ('snapshot versions'), and a clear scope ('for a specific file path on an agent'). This distinguishes it from sibling getters like slide_get_snapshot or slide_search_agent_files even without naming them.

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 gives no explicit guidance about when to prefer this tool over related siblings, and it does not mention exclusions or prerequisites. The only implied use is 'when you need snapshot versions,' which is not enough to route an agent reliably among the many file/snapshot tools in the sibling list.

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