dotloop_get_custom_templates

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

No annotations are provided, so the description must carry the full burden. It only states 'get', implying read-only, but does not disclose what the call returns (e.g., list of templates) or any prerequisites like permissions. The description is too brief to be informative.

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 a single sentence, which is concise but overly minimal. While it avoids verbosity, it sacrifices clarity and completeness. A balance of brevity and informativeness is needed.

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 one parameter with no description in the schema, and there are many sibling tools with overlapping functionality, the description should provide more context about what 'custom templates' means and how this tool differs from others like dotloop_get_default_templates. The presence of an output schema is noted but not leveraged.

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%, and the description adds no meaning to the profile_id parameter. There is no explanation of what profile_id is or how to obtain it, leaving the agent without necessary context.

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 'Get custom Dotloop templates' clearly states the verb (get) and resource (custom templates). However, it does not differentiate from sibling tools like dotloop_get_default_templates or dotloop_get_templates_by_type, which also retrieve templates with specific scopes.

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 given on when to use this tool versus alternatives. For example, there is no mention that this tool retrieves only custom templates (not defaults) or what the profile_id parameter represents.

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