ai_get_active_info

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

There are no annotations, so the description must carry the read-only signal; '获取...信息' clearly conveys a retrieval operation with no mutation. It also enumerates the observable outputs, giving the agent a good model of behavior, though it doesn't cover edge cases such as no active document or units for dimensions.

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 front-loads the operation and then provides a focused list of return fields. There is no filler, tautology, or redundant restating of the input schema.

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 parameterless getter with no output schema, the description is nearly complete: it tells the agent what to retrieve and what data will be available. It stops short of specifying units, data types, or behavior when no document is open, but these are minor for this level of complexity.

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?

With zero parameters, the schema leaves nothing ambiguous and the baseline is 4. The description's list of returned information adds semantic context even though no parameter documentation is needed.

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?

Description uses a concrete verb (获取/get) and a specific resource (当前活动文档信息), and enumerates the exact data returned—name, dimensions, path count, text frame count, and open document count. The mention of Illustrator and 'active document' distinguishes it from siblings like ps_get_active_info and ai_list_documents.

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 phrase 当前活动 implies this tool should be chosen when the AI needs the active Illustrator document's properties rather than a list of all documents, but it never explicitly names alternatives or says when not to use it. The when-to-use guidance is therefore implied rather than stated.

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