ghl_agent_studio_execute_deprecated

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

The description reveals that the tool is a write operation (OAuth scope agent-studio.write), returns non-streaming JSON, and manages sessions via executionId. These go beyond the minimal annotations (readOnlyHint false, etc.). No contradictions with annotations.

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 unnecessarily verbose, with the deprecation warning repeated three times. Session management details are included but could be more structured. A more concise and organized description would improve readability.

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 complexity of the nested input schema and lack of output schema, the description covers core behavior (execution, session handling, required fields) and deprecation. It omits error handling and response structure, but is adequate for a deprecated tool.

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 description adds value beyond the 33% schema coverage by explaining the purpose of executionId for session continuity, noting that versionId defaults to latest production version, and emphasizing that locationId is required. This compensates for the schema's lack of detail.

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 that the tool executes an agent and returns a non-streaming JSON response. It specifies the verb 'Executes' and the resource 'agent', and distinguishes itself by noting deprecation and directing to an alternative sibling tool.

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 explicitly recommends using the non-deprecated sibling tool 'ghl_agent_studio_execute' instead. It also provides conditions (agent must be active, locationId required) and detailed session management instructions for first and subsequent messages.

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