tealfabric_get_document_metadata

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get metadata' implies a read-only operation, but the description does not disclose what happens for missing files, what metadata fields are returned, whether tenant resolution affects behavior, or any error semantics.

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 one short sentence that front-loads the purpose and contains no filler. It is appropriately concise, though it sacrifices some useful behavioral context for brevity.

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 simple read tool with fully documented parameters, this definition is minimally workable: the agent knows the intended operation and has file_path guidance via the schema. However, because there is no output schema and no annotation, the return contents, error behavior, and edge-case handling are left unspecified.

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 100%, and the schema already documents file_path with an example and tenant_id with its default. The tool description adds no additional parameter-level meaning beyond referring to the target as a 'document/file,' so the baseline score of 3 is appropriate.

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 states a clear action and resource: 'Get metadata for a document/file in Tealfabric documents storage.' It distinguishes this from sibling tools like download, upload, move, or delete by focusing on metadata retrieval. It does not enumerate what metadata is returned, but the core purpose is unambiguous.

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 explain when to use this tool instead of tealfabric_list_documents or tealfabric_download_document, nor does it mention preconditions such as the file needing to exist.

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