get_time_config

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the specific data returned (frame rate, time range, current frame), which is useful. It doesn't mention return format, units, or whether the time range is in frames or seconds, but for a simple getter with no parameters, this is acceptable.

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 two short sentences, one in Chinese and one in English, with zero wasted words. The key information (what is read) is front-loaded. It is appropriately sized for a zero-parameter getter.

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 zero-parameter read-only getter, the description is nearly complete. It names the three pieces of data returned. The only minor gap is not describing the return format or units, but with no output schema and no parameters, an agent can still invoke it correctly and interpret the result at a basic level.

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?

The tool has zero parameters, so there is no parameter semantics burden on the description. The schema is trivially complete (100% coverage with no properties). The description correctly implies no input is needed, which is the only relevant semantic information.

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 tool reads frame rate, time range, and current frame, which is a specific verb+resource combination. It distinguishes itself from set_time_config (the sibling that writes these values) and from anim_get_frame (which only gets the current frame). However, it doesn't explicitly name those siblings, so it doesn't fully earn a 5.

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 implies a read-only query use case, and the readOnlyHint annotation reinforces that. It doesn't explicitly state when to use this over alternatives like anim_get_frame or set_time_config, but the read-only framing and the sibling list make the intended usage reasonably clear. No explicit exclusions or alternative routing are provided.

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