get_file_properties

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Get properties' without indicating authentication requirements, read-only nature, error handling, or limitations. Critical details like whether extended parameter affects behavior or what happens when multiple identifiers are provided are missing.

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, well-structured sentence that conveys the core purpose with key identification methods. It is efficient but could include more detail without becoming verbose.

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?

With no output schema, the description should outline return values (e.g., property fields or structure). It does not. Also, given the tool's placement among many file operations, it fails to help the agent decide when to use this tool instead of get_file_id or list_files. The lack of required parameters is not addressed.

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 67% (path and file_id have descriptions, extended does not). The description adds the clarification that path can be 'Remote path or File URI', which goes beyond the schema. However, it does not explain the 'extended' parameter's purpose or default value, leaving a gap for one parameter.

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 that the tool retrieves file/folder properties and specifies three identification methods (path, File URI, id). It distinguishes from sibling tools like list_files or get_download_url by focusing on properties. However, it does not define what 'properties' includes, which slightly reduces clarity.

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 on when to use this tool versus alternatives such as get_file_id, get_download_url, or list_files. The description does not mention prerequisites, typical use cases, or exclusionary conditions, leaving the agent to infer usage from the tool name alone.

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