derivation_handoff_status

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

No annotations are provided, so the description carries the transparency burden. It explicitly says 'Returns: Handoff status and suggestions', indicating a read-only informational nature. It adds context about tool capabilities and handoff advice, but does not specify session handling or edge cases; for a status tool, this is adequate but not rich.

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 concise and well-structured, with a clear title line, a numbered list of three purposes, and a Returns line. It is front-loaded with the main purpose and contains no redundant or extraneous information. The formatting enhances readability.

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 simple status tool with an output schema, the description covers the core purpose and the three key areas it addresses. However, it omits session_id semantics and lacks explicit usage context relative to the many sibling derivation tools. The completeness is moderate, sufficient for basic understanding but with clear 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?

The schema has one optional parameter (session_id) with 0% description coverage, and the description does not mention it at all. Since the parameter is optional with a default, the omission is less critical, but the description adds no meaning beyond the schema, failing to compensate for the low 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 it shows Handoff status and available options, with a specific verb ('顯示') and resource. It further enumerates three distinct purposes: NSForge capabilities, what to hand off to SymPy-MCP, and current derivation status, which helps distinguish it from sibling status tools like derivation_status. However, '可用選項' (available options) is somewhat vague.

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 implies usage for understanding handoff between NSForge and SymPy-MCP, but it does not explicitly contrast with alternative tools or provide when-not-to-use guidance. The mention of 'what needs to be handed off' suggests a decision-support role, but exclusions or alternatives are absent.

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