dotloop_list_profiles

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. It fails to specify whether the list includes all profiles, requires authentication, or exhibits any pagination or ordering. The single sentence offers no behavioral context.

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 very concise (one sentence) and front-loaded. However, it lacks structure and additional helpful context that would warrant a higher score. While not verbose, it may be too sparse for an agent to fully understand the tool's scope.

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 lack of annotations and the presence of an output schema, the description does not explain what the output contains (e.g., list of profile IDs or full objects). It also does not cover any scope or limitations, making it incomplete for a tool in a large set of siblings.

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 tool has zero parameters, and the schema coverage is trivially 100%. Although the description adds no parameter-specific meaning, the baseline for zero parameters is 4, and the description does not provide misleading information.

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 'List Dotloop profiles' clearly identifies the verb 'list' and the resource 'profiles', making the basic purpose understandable. However, it does not differentiate from the sibling tool 'dotloop_get_profile' which retrieves a single profile, so it lacks explicit sibling distinction.

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 provides no guidance on when to use this tool versus alternatives such as 'dotloop_get_profile' or other listing tools. There is no mention of context, prerequisites, or situations where this tool is appropriate.

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