cubism_get_document

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

No annotations are provided, so the description carries full burden. It states it gets '详细信息' but does not disclose behavioral traits like idempotency, side effects, or access requirements. The presence of an output schema mitigates the lack of return description, but overall transparency is minimal.

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 extremely concise, with a single sentence front-loading the purpose, followed by a clear Args section. No unnecessary words.

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 presence of an output schema, the description is sufficient for a simple retrieval tool with one parameter. It explains the parameter source and the core action, leaving details of the output to the schema.

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 0%, but the description adds meaning by explaining 'document_uid' as '文档 UID' and its source from cubism_get_documents. For a single parameter, this adds useful context, though it does not specify format or constraints.

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 '获取单个文档的详细信息' (get detailed information of a single document), providing a specific verb and resource. It implicitly distinguishes from the list tool cubism_get_documents by specifying '单个' (single), but does not explicitly contrast with other siblings.

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 only hints that document_uid can be obtained from cubism_get_documents, but lacks explicit guidance on when to use this tool versus alternatives, no when-not or exclusion criteria.

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