ghl_forms_get

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

With no annotations available, the description carries the full burden of behavioral disclosure. It only states 'Get forms' and does not mention read-only nature, return format, pagination, or any side effects. The agent has no idea what to expect from invoking this tool.

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, but this is under-specification rather than efficient conciseness. It lacks essential details about the resource being retrieved, so it does not earn its place as a useful description.

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?

The tool is a simple getter, but the description provides almost no contextual information. Without an output schema or behavioral details, the agent cannot understand the return value, the scope of 'forms', or any constraints. The description is inadequate for effective tool selection and invocation.

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?

There are zero parameters, and the schema is empty with 100% coverage. The baseline for no parameters is 4, and the description does not need to explain parameter meanings. Since there is nothing to add, the schema and lack of parameters suffice.

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 forms' specifies a verb and resource, but it essentially restates the tool name (ghl_forms_get) and provides no context about what forms are or how they are scoped. It does not differentiate from sibling getter tools like ghl_pipelines_get or ghl_knowledge_base_list, making it minimally informative.

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 versus alternatives. The description gives no indication of prerequisites, filtering options, or scenarios where this tool is appropriate, leaving the agent without any decision support.

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