dotloop_get_folder

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

No annotations are present, and the description does not disclose behavioral traits such as whether the tool is read-only, what happens if the folder is not found, or if it requires specific permissions. The word 'Get' implies a read operation, but no additional context is given. With no annotations, the description carries the full burden and fails to provide sufficient behavioral insight.

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 (one sentence) but lacks substance. It is under-specified rather than concise; it does not earn its place as it fails to provide useful information. A concise description should be informative without verbosity, but this is too minimal.

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 tool has 5 parameters (3 required), an output schema, and numerous siblings, the description is insufficient. It does not explain the input parameters, expected output (though output schema exists, it could still describe return value briefly), or how it differs from listing folders. The description misses critical context for effective use.

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%, meaning no parameter descriptions exist in the schema. The description does not add any meaning to the parameters beyond their names and types. For example, it does not explain what profile_id, loop_id, folder_id refer to, or the purpose of include_archived and include_documents. The tool has 5 parameters, and the description adds no semantic value.

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 'Get one Dotloop loop folder,' which clearly indicates the verb and resource. However, it does not differentiate from sibling tools like dotloop_list_folders, which lists folders, or dotloop_get_loop, which gets a loop. The purpose is adequately clear but lacks specificity to distinguish it from alternatives.

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 guidance is provided on when to use this tool over siblings. For instance, there is no mention that this tool is for retrieving a single folder by ID, while list_folders is for obtaining a list. The description offers no context for usage decisions.

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