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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds approval-related context: MCP approval requirements are configurable by the organization administrator and business workflow approvals always apply; this is useful behavioral context but remains somewhat vague and does not cover pagination or return behavior.

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 two sentences and front-loads the core purpose and scope. The approval sentence is relevant behavioral context, though slightly tangential, and the overall wording is 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?

The description adequately defines the target-location domain and its exclusions for a list/search tool, and an output schema exists so return values need not be explained. However, with four undocumented parameters and 0% schema description coverage, the description leaves important filtering and pagination semantics unaddressed.

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%, and the description mentions only that the tool supports listing/searching. It does not explain the four parameters—id, limit, offset, and search—or how they should be used, so it does not compensate for the lack of schema descriptions.

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 a specific verb and resource: "List/search Target Locations." It defines the resource as desired expansion markets and target cities shared with brokers, and explicitly distinguishes it from existing sites and the Target retail brand, which helps separate it from list_sites and brand-related confusion.

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 clear usage context by describing the domain as desired expansion markets and target cities shared with brokers. It also provides exclusions—not existing sites or the Target retail brand—though it does not explicitly name alternative sibling tools such as list_sites.

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