list_incoming_transfers

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

In the absence of annotations, the description discloses the GET HTTP method, the API endpoint, and the fact that entries include a preview_path for deep-linking. It also mentions the version requirement. It does not explicitly state that the operation is read-only, but the nature of listing transfers implies it. Overall, it provides sufficient behavioral context for a list 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 extremely concise—two sentences covering purpose, scope, version, preview_path, and the HTTP endpoint. Every sentence adds value, with no redundancy or fluff.

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?

While the description covers the main purpose and pagination parameters, it lacks details about the return structure beyond the preview_path field. Since no output schema is provided, the description should describe what fields to expect in each entry. This omission leaves the agent uncertain about the response format, making the context incomplete for a well-informed 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?

Both parameters (after, limit) are fully described in the input schema, achieving 100% schema description coverage. The description does not add any new meaning or usage guidance beyond what the schema already provides, so it meets the baseline without additional value.

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 specifies the action ('List pending project transfers'), the scope ('OFFERED TO the authenticated wallet'), and distinguishes from siblings like list_outgoing_transfers by emphasizing 'incoming'. It also adds version info and the API endpoint, leaving no 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?

The description provides clear context for when to use the tool (to view incoming transfers) but does not explicitly state when not to use it or suggest alternatives like list_outgoing_transfers or preview_project_transfer. The purpose is understandable, but usage guidance is implicit rather than explicit.

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