get_upload_config

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

With no annotations provided, the description carries the full disclosure burden. It successfully indicates what contextual information is returned (file types, size limits) and hints at the 'constraints' understanding purpose, but lacks details on caching behavior, authentication requirements, or whether the configuration is user-specific vs global.

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?

Optimal two-sentence structure with zero waste. First sentence establishes the core function and return value categories; second sentence establishes the temporal context (pre-upload). Information is perfectly front-loaded and appropriately sized for the tool's simplicity.

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?

Given the tool has no parameters, no annotations, and no output schema disclosed, the description adequately covers the essential information: what configuration categories are returned (file types, size limits) and the operational context (pre-upload validation). Minor gap in not describing the data structure of the response, but acceptable for a simple configuration retrieval tool.

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?

Input schema contains zero parameters, triggering the baseline score of 4 per evaluation rules. The tool requires no configuration to retrieve the upload constraints, which is appropriate for a global configuration endpoint.

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?

Clearly specifies the action (获取/get) and resource (图片上传配置/image upload configuration), including specific configuration aspects like file types and size limits. Effectively distinguishes from sibling 'upload_image' by clarifying this retrieves constraints rather than performing the upload.

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?

Explicitly states when to use the tool: '上传图片前先调用此接口' (Call this interface before uploading images). Provides clear prerequisite context, though it could explicitly name the subsequent 'upload_image' tool as the next step in the workflow.

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