saas_api_get_saas_locations

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the token-level requirement, which is useful context beyond annotations. However, it doesn't describe pagination, error behavior, or response format, so it adds limited behavioral value.

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 a single concise sentence that front-loads the action and includes a critical access constraint. It is not verbose and every word adds some value, though it could be more informative.

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?

This is a simple GET tool with two required parameters but no output schema and no parameter descriptions. The description only provides the action and token requirement, missing crucial details about parameters, pagination, and response format. For an agent to call this correctly, more context is needed.

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 description coverage is 0% – parameters `companyId` and `page` have no descriptions in the schema, and the description doesn't explain them at all. The tool description fails to compensate for the lack of parameter documentation, leaving agents without any guidance on what values to provide.

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 'Get SaaS Locations' – a specific verb and resource. It also adds an important access requirement (agency-level token). However, it doesn't differentiate from similar sibling tools like saas_api_locations or the deprecated variant, so it's not a 5.

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 gives a prerequisite (agency-level token) but no explicit guidance on when to use this tool vs alternatives like saas_api_locations or the deprecated version. It doesn't mention exclusions or alternative tools, so the usage context is incomplete.

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