get_table_template

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds the session-scoping context ('当前会话') but doesn't disclose behavior when no session is active, whether it errors, or what the returned JSON structure looks like. Minimal beyond the name.

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, efficient sentence that front-loads the action and resource. No wasted words or redundant restatement of the name.

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 getter, the description is adequate but lean. Given the dense sibling set of session-related tools (create_preview_session, get_session, set_table_template), it doesn't clarify what 'current session' means or what happens without an active session. An agent might call it at the wrong time.

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 the schema and description have nothing to document. Baseline 4 applies since there is no parameter burden to compensate for.

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 states a clear verb ('获取'/get) and resource ('表格模板 JSON'/table template JSON), and scopes it to the current session. It distinguishes itself from set_table_template (which sets the template) but doesn't differentiate from similar getters like get_template_detail, get_schema, or get_data_config.

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 is provided on when to use this tool versus its many sibling getters (get_template_detail, get_schema, get_data_config) or which session state is required. An agent cannot determine the right selection context from the description alone.

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