ghl_voice_ai_create_agent

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

Annotations already indicate a write operation (readOnlyHint=false, destructiveHint=false). The description adds the endpoint and scopes but does not disclose what the tool returns upon success, whether it is idempotent, or side effects like creating a new agent in the system. With minimal annotation coverage, the description should provide more 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 short (three lines), but it front-loads the core purpose. It includes technical details like endpoint and scopes, which are useful but could be more structured. Some waste is acceptable given the schema's richness.

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 description does not explain what the tool returns after creation (no output schema provided). It lacks mentions of prerequisites (e.g., location must exist) or constraints beyond the schema. For a complex creation tool, this is incomplete.

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 input schema has 100% coverage with detailed descriptions for all parameters. The tool description adds no additional parameter-level meaning beyond what the schema already provides. Baseline score of 3 is appropriate given the schema's thoroughness.

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 clearly states 'Create a new voice AI agent configuration and settings', which identifies the specific verb and resource. The title 'Create Agent' reinforces this. It distinguishes from sibling tools like ghl_voice_ai_patch_agent or ghl_voice_ai_delete_agent by specifying creation.

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 endpoint and OAuth scopes but offers no guidance on when to use this tool versus alternatives (e.g., ghl_voice_ai_patch_agent for updates). It does not mention prerequisites or contextual cues for selection.

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