get_lark_doc_content

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

The description provides no behavioral information beyond the basic action. With no annotations, the description should disclose safety (e.g., read-only), authentication requirements, or error behavior, but it says nothing. This leaves the agent blind to important execution traits.

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 short, but this is under-specification rather than conciseness. It lacks structure, such as separating the main description from parameter details. Every sentence does not earn its place because more essential information is omitted.

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 no output schema, no annotations, and a single parameter, the description should explain the return value, expected behavior, and constraints (e.g., URL must be accessible). It provides nothing, making it wholly incomplete for an AI agent to use correctly.

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 input schema has no description for the 'documentUrl' parameter, and the description only repeats the parameter name ('documentUrl: Lark document URL') without clarifying format, validity rules, or examples. Schema coverage is 0%, and the description fails to compensate.

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 action ('Get') and the resource ('Lark document content'), distinguishing it from the sibling 'search_wiki' which searches rather than retrieves content. However, it does not specify the format or scope of 'content' (e.g., plain text, structured data).

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 usage guidance is provided. The description does not mention when to use this tool instead of 'search_wiki' or any other alternative. It simply states the function without context.

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