td_get_file_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get detailed info' implies a safe read, but it does not specify what 'detailed info' contains, whether file content is returned or just metadata, or any errors or permissions. This is thin for a tool with no structured behavioral 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?

A single, compact sentence that states the core action immediately. There is no redundant filler, and the parenthetical adds useful clarifying context without bloating the description.

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 tool with no output schema and no annotations, the description is too minimal. It does not explain what the returned info will look like, how this relates to the media message, or how it differs from the many similar sibling tools. The required parameters are clear, but the broader invocation context is incomplete.

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 parameters dialog and messageId are already well documented. The description adds no new parameter-level semantics, but the schema handles that burden; a baseline score of 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?

The description clearly states the action ('Get detailed info') and the target resource ('a specific file'), with the parenthetical '(message with media)' clarifying the domain context. However, it does not explicitly distinguish itself from the closely named sibling td_get_media_info.

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?

There is no guidance about when to use this tool versus alternatives such as td_list_files, td_search_files, or td_get_media_info. The description gives no context for selection or exclusions, leaving the agent to infer appropriateness.

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