tc_get_file

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds value by noting it returns 'the raw file JSON from the API', restricts to the 'latest version', and explains that project_id resolves the region. No contradiction with annotations.

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 compact and front-loaded: purpose, args, return. Every sentence provides necessary information without repeating annotation data or schema details.

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 read-only metadata operation, the description fully covers what the tool does, the two required parameters, and the return format. The output schema exists to provide field details, and annotations cover safety, so the tool is adequately specified.

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 compensates by explaining both parameters: project_id is the project the file belongs to and resolves the region, while file_id is identified as coming from tc_list_folder. This goes beyond the bare schema property names.

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 starts with 'Get metadata of a file (latest version): name, size, revision, dates,' which is a specific verb plus resource. The 'latest version' qualifier distinguishes it from sibling tools like tc_list_file_versions and tc_download_file, making the tool's purpose clear.

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?

It provides clear invocation context: project_id resolves the region, and file_id comes from tc_list_folder. However, it does not explicitly state when to prefer this over tc_download_file or tc_list_file_versions, so it lacks an explicit exclusion.

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