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

Annotations only cover safety flags (readOnly=false, idempotent=false, destructive=false). The description adds real behavioral context beyond them: a metered, authenticated identity read must precede the call, existing metadata must match, and it performs no clone/scan/install. It omits what the response returns and any failure/rollback behavior, but the auth prerequisite and matching requirement are meaningful disclosures.

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?

Three tight sentences with no filler, and the core action is front-loaded ahead of constraints. The 'metered authenticated native identity read' phrasing is jargon-dense but earns its place as a precondition.

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 7-parameter write tool with no output schema and only shallow annotations, the description covers prerequisites and exclusions but leaves most parameters undefined and says nothing about the result of the call. Adequate but with clear gaps given the schema's 0% coverage.

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 7 required parameters, so the description carries the full explanatory burden. It only gestures at 'stable project/target UUIDs' and metadata matching, leaving deviceId, workspaceGrantId, environment, relativePath, and displayName entirely unexplained. This is insufficient compensation for a 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?

States a specific verb and resource: 'Register one owner-selected repository location.' An agent can tell this apart from project_target_list or project_target_resolve by the act of registering. It stops short of naming those siblings explicitly, so it lacks full differentiation.

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?

Gives a clear precondition ('after a metered authenticated native identity read') and negative scope ('No clone, scan, install or environment fallback'), telling the agent both when this applies and what it will not do. It does not name an alternative tool for the excluded cases, so it falls just short of explicit when/when-not routing.

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