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

The description explicitly discloses the major side effects: 'Closes all roster bot positions and returns capital to the wallet,' which is significant for a mutation tool. It does not mention reversibility, preconditions, or failure modes, and with no annotations provided the description carries the full disclosure burden yet only partially meets it.

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 efficiently structured: a one-line summary, then the behavioral effect, then minimal Args and Returns lines. It is free of bloat and front-loads the key action and side effects. The Args line is redundant but harmless, and the overall length is appropriate.

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 mutation tool with no annotations and 0% schema coverage, the description omits prerequisites, reversibility, error conditions, and parameter provenance. It covers the main action and side effects but leaves an agent without enough information to use the tool safely and correctly, such as whether the fund can be reactivated or what happens to fund state.

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 description provides 'fund_id: The fund's ID,' which merely restates the parameter name and title without adding semantic content. At 0% schema description coverage, this is a weak compensation attempt that fails to explain the parameter's format, source, constraints, or relationship to other fund operations.

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 clear action ('Deactivate Manager Mode') and its primary effect ('Closes all roster bot positions and returns capital to the wallet'). The verb, resource, and behavioral outcome are specific enough to distinguish it from activate_fund and most siblings. However, it doesn't explicitly differentiate from close_fund, and 'returns to the main platform router' is ambiguous without more context.

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 when-to-use guidance is provided; the description never states prerequisites (e.g., the fund must be in manager mode), conditions, or how this differs from close_fund. An agent cannot determine from the description alone when to invoke this tool versus a sibling. The 'Args' and 'Returns' lines are present but add no decision guidance.

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