preview_project_transfer

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

Discloses secret values are never returned, HTTP method (GET), and auth requirement. Without annotations, description carries burden; provides good context.

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?

Concise, front-loaded action sentence, no redundant information, well-structured.

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?

Complete for a simple preview tool: covers return content, auth condition, HTTP method, and version requirement. No gaps.

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?

One parameter with full schema description. Description adds version requirement (v1.59+), but parameter semantics already covered by schema.

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?

Describes fetching a preview document for project transfers with specific return fields (project name, domains, secrets, etc.), distinguishing it from related tools like accept or cancel.

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?

States caller must be from_wallet or to_wallet, implying usage before accepting a transfer. Could clarify when not to use, but adequate.

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