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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description goes beyond them by disclosing that the read is 'metered' (cost implication), that it 'never switches device or creates metadata' (explicit side-effect exclusion), and by enumerating the possible resolution states. It does not explain why idempotentHint is false for a read, but nothing is contradicted.

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 compact sentences with the core purpose and the return states front-loaded, and the side-effect exclusions placed second. Dense but no filler; the metered/identity phrasing is the only mild cost.

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?

With no output schema, the description usefully enumerates the return states, and annotations cover the safety profile. But for a three-parameter tool with 0% schema coverage, the unexplained previousTargetId leaves a real hole in an otherwise adequate definition.

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%, so the description carries the full burden, yet it only alludes to 'one registered target' and never explains projectId, targetId, or the optional previousTargetId. The role of previousTargetId in particular is completely opaque from both the schema and the description.

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 ('identity read for one registered target') and enumerates the return states (resolved/unknown/offline/stale/mismatch), which distinguishes it from siblings like project_target_list and project_target_register. It is somewhat jargon-heavy ('metered native identity read'), but an agent can tell what the tool does.

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 phrase 'On-demand metered' implies this is invoked deliberately rather than as part of a flow, and 'never switches device or creates metadata' acts as a when-not signal. However, it never names an alternative (e.g., project_target_list or project_identity) or states the condition that selects this tool over them, so usage is only implied.

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