ghl_saas_update_rebilling_deprecated

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

Annotations already indicate readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds the token requirement but lacks further behavioral insights (e.g., side effects, reversibility). No contradiction 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 contains redundant deprecation statements (two similar lines) and repeats the endpoint URL. It could be more concise while maintaining clarity.

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?

For a deprecated tool with sibling replacement, the description adequately provides deprecation guidance and authentication requirement. However, it lacks details about the response or error scenarios, which are not covered by annotations or output schema.

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% with descriptions for all parameters. The description adds no new parameter-level information beyond the schema, so baseline 3 is appropriate.

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 'Bulk update rebilling for given locationIds,' which is a specific verb+resource. The tool name includes '_deprecated' and the description explicitly mentions it is superseded, differentiating it from the non-deprecated sibling 'ghl_saas_update_rebilling'.

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 states 'DEPRECATED per spec — superseded by POST /saas/update-rebilling/{companyId}' and prefers the documented replacement. It also notes 'REQUIRES AN AGENCY-LEVEL (Company) TOKEN,' giving clear when-to-use and when-not-to-use guidance.

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