preview_project_transfer

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

No annotations exist, so the description fully carries the burden. It discloses what the return payload contains (including sensitive data like secret names but not values) and the authentication requirement. It does not mention rate limits or side effects, but for a read-only preview this is sufficient.

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, but the first sentence is long and lists many return fields. It is still readable and front-loaded with the core action. Could be slightly more concise, but not wasteful.

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?

Given the single parameter, no output schema, and no annotations, the description provides a thorough list of return fields, version requirement, and caller prerequisite. It is nearly complete for guiding an agent, though error conditions could be added.

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?

The single parameter transfer_id already has a detailed description in the input schema (100% coverage). The main description adds nothing beyond the schema, so it meets the baseline for high coverage.

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 the verb 'Fetch' and the resource 'preview document for a project transfer', distinguishing it from sibling transfer tools like accept_project_transfer or initiate_project_transfer. It also mentions the API endpoint for precise identification.

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 specifies that the caller must be a party to the transfer and that the tool is kind-agnostic (works for wallet and email transfers). Although it does not explicitly contrast with siblings, the context makes it clear this is a preview step before acting.

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