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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description does add real beyond-annotation behavior: offline locations remain registered and there is no fallback or repository scan, which tells the agent results may be stale/offline and are not derived. The phrasing is terse and unexplained, limiting the credit.

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?

Two short sentences with no filler, but they are sentence fragments rather than a front-loaded statement of purpose, and vague wording ('Offline locations stay registered') costs clarity per word.

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?

No output schema exists, yet the description does not describe the returned target shape, pagination via afterTargetId, or ordering. For a listing tool with three undocumented parameters and only annotation-level safety info, the description is materially incomplete.

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% across three parameters (projectId, limit, afterTargetId pagination), and the description supplies no parameter meaning at all — not the required project UUID, the limit default of 20, or the cursor semantics of afterTargetId. Nothing compensates for the total coverage gap.

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 is a noun-phrase fragment ('Explicit device/workspace/environment targets and verification metadata') that describes the resource but never states the verb — only the title 'List project locations' reveals it is a listing operation. Siblings project_target_register and project_target_resolve are not addressed, so the agent must infer the distinction from the name alone.

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?

'No fallback or repository scan' hints at a scope boundary but reads as a cryptic negative rather than a when/when-not rule. It never tells the agent when to pick this over project_target_register, project_target_resolve, or project_snapshot, and no prerequisites are given.

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