derivation_status

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It states that it returns the current session status but does not disclose whether the tool is read-only, requires an active session, has side effects, or how it behaves when no session exists. This leaves important behavioral traits unspecified.

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 brief, but the brevity is under-specification rather than conciseness. It repeats the same idea in the Returns section without adding value, and every sentence is merely a restatement of the tool's name, not informative content.

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?

Although an output schema exists, the description is still incomplete. It does not explain what 'current session' means, whether session_id is required to select a non-current session, or how this status differs from derivation_handoff_status. The tool lacks the contextual information needed to use it correctly in a multi-tool session management workflow.

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 input schema has one parameter (session_id) with a default and 0% description coverage. The description does not mention this parameter at all, nor does it explain how it relates to the 'current session' concept. The agent is left without any semantic understanding of the parameter beyond its name.

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 states a specific action ('取得' = get) and resource ('當前會話狀態' = current session status), clearly distinguishing it from session listing tools like derivation_list_sessions. However, it does not differentiate from the similar-sounding derivation_handoff_status, so it's not fully clear what makes this status distinct from that one.

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 provided about when to use this tool versus alternatives. The description does not mention context, prerequisites, or exclusions, leaving the agent to guess when this status tool is appropriate compared to other session-related tools.

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