ghl_saas_get_locations_deprecated

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint false. Description adds deprecation context and auth requirement, which are beyond the annotations. No contradictions.

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?

Description is somewhat messy with repeated brackets and redundant deprecation notice. While relatively short, it could be more streamlined and front-loaded.

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 absence of an output schema, description does not explain the response structure or what fields are returned. While annotations cover safety, the description leaves the output format unspecified, which is a gap.

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% and description mostly repeats schema info ('Pagination params: page — pass them to page through full result sets'). Does not add new semantic meaning beyond what the schema already provides.

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?

Description clearly states 'Get SaaS Locations' and 'Fetch all SaaS-activated locations for a company with pagination', identifying the specific verb and resource. It also distinguishes from siblings by marking itself as deprecated and noting the superseding endpoint.

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?

Explicitly states deprecation status ('DEPRECATED per spec — superseded by...') and the requirement for an agency-level token ('REQUIRES AN AGENCY-LEVEL (Company) TOKEN'). Provides clear guidance to prefer the replacement and mentions pagination usage.

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