ghl_estimate_send

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

Annotations (readOnlyHint=false) indicate mutation, but the description adds no behavioral context beyond the endpoint. It does not disclose potential side effects (e.g., triggering notifications) or state changes, which are critical for a sending action.

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 and includes technical details (endpoint, scopes) but is efficient. However, it could better structure information for agent consumption without losing conciseness.

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's complexity (nested body, enums, no output schema), the description is incomplete. It does not explain the purpose of the body fields, required action, or output, leaving significant gaps for correct 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?

Schema coverage is 100%, so the schema already documents parameters. The description adds no additional meaning beyond the schema, meeting the baseline requirement but offering no extra value.

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 states 'Send Estimate' and 'API to send estimate by estimate id', clearly indicating the action and resource. This distinguishes it from sibling tools like ghl_estimate_create or ghl_estimate_update, though it lacks specifics on what 'send' entails.

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 on when to use this tool versus alternatives (e.g., ghl_estimate_create, ghl_estimate_update). The description does not mention prerequisites or context, leaving the agent uninformed about appropriate usage scenarios.

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