anythingllm_get_document

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

The annotations already declare the tool as read-only and idempotent. The description adds context about the document identifier format and that it returns metadata, which is consistent with the annotations. No extra behavioral details (e.g., error cases) are given, but the low-risk nature is covered.

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 compact and well-structured: a clear purpose statement, an explanatory note on the parameter, and an Args block. Every sentence adds value.

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?

With a single parameter, an output schema available, and annotations provided, the description sufficiently covers the tool's usage. The parameter is fully documented, and the tool's read-only nature is clear.

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 schema has no description for doc_name, but the description fully explains that it is the internal document identifier returned by list_documents, with an example. This compensates perfectly for the 0% schema coverage.

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 tool retrieves metadata and details for a specific document, identified by its stored name. It distinguishes itself from list_documents by focusing on a single document and explains the identifier format.

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 explains that doc_name comes from list_documents, indicating when this tool is appropriate (after listing). It does not explicitly mention alternatives or exclusions, but the context of retrieving a specific document is clear.

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