transfer_credential

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'transfer' implying mutation, but does not explain side effects (e.g., whether the credential is removed from the original owner, whether it affects active workflows, or required permissions). The agent cannot infer the impact of calling this tool.

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 a single sentence that conveys the core purpose efficiently. It avoids redundancy and is well front-loaded. However, given the lack of detail, the conciseness is a double-edged sword; the sentence earns its place but does not fully fulfill the tool's informational needs.

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 tool with three parameters, no annotations, and no output schema, the description is incomplete. It fails to specify how the credential is identified, what happens when both 'projectId' and 'newOwnerId' are provided, or the response format. An agent would lack sufficient context for correct invocation.

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%, and the description does not clarify the three parameters. The hint 'to a different project or owner' loosely maps to 'projectId' and 'newOwnerId', but does not explain their interplay, data types, or constraints. The required 'id' is utterly unexplained. The tool relies on parameter names alone, which is insufficient.

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 specifies the verb 'transfer' and the resource 'credential', and states the destination ('different project or owner'), which is clear and distinguishes from sibling tools like 'list_credentials' or 'delete_credential'. However, it does not clarify if the operation is a move or a copy, leaving a slight ambiguity.

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 guidance is given on when to use this tool versus alternatives (e.g., 'resolve_credential_alias', 'list_credentials'). The description does not mention prerequisites, scenarios, or exclusions, leaving the agent without contextual decision-making support.

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