project_manage

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

Discloses idempotency and success behavior for stop, and persistence for settings_set. No annotations are provided, so the description carries the full burden. Missing details on error behavior (e.g., key not found), permissions, or side effects.

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?

Well-structured with a summary and bullet-pointed ops. Each sentence provides useful information. Slightly lengthy but efficient for the tool's complexity.

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?

Covers the three operations, idempotency, parameter constraints, and the resource form alternative. With an output schema assumed present, return values need not be described. Lacks error handling details but is fairly complete for a multi-op tool.

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?

Explains the op enum values and their parameter requirements (stop: no params, settings_get: key, settings_set: key, value). Adds context for session_id placement. However, does not fully describe the params object structure or all properties, and schema description coverage is 0%.

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 lists three operations (stop, settings_get, settings_set) and their purposes. However, the initial phrase 'Project run/stop' is misleading because only stop is provided, lacking the run operation. The resource form hint differentiates from active-session reads.

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?

Provides intra-tool guidance for stop (idempotent, no extra params, session_id placement) and recommends resource forms for reads. However, lacks inter-tool differentiation from siblings like project_run or game_manage, leaving the agent to infer when to use this tool over alternatives.

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