saas_api_get_location_subscription_deprecated

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds the critical constraint that an agency-level token is required (not a location PIT), which is beyond the annotations. However, it omits the deprecation status, which is a behavioral trait (it will likely be removed) not covered by 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?

One sentence with zero fluff, front-loads the purpose and then the auth requirement. Extremely efficient.

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 simple getter with annotations covering safety, the description is mostly complete, but it fails to mention that the tool is deprecated (despite the name) and that a non-deprecated alternative exists. This is important context for an agent to make routing decisions.

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 has 100% coverage of both parameters. The description adds no additional parameter information beyond what the schema already provides. Baseline of 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 the verb 'Get' and resource 'Location Subscription Details', and adds a specific authentication nuance. However, it does not explicitly differentiate from the non-deprecated sibling saas_api_get_location_subscription, which limits its ability to distinguish between them.

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?

It provides a prerequisite (agency-level token) but does not give any guidance on when to use this tool vs alternatives, particularly the non-deprecated version. No exclusions or usage context beyond the auth note.

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