problem

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known, and the description adds only the write precondition. It does not say which action is destructive (solve? log?), what happens to existing data, what authorization is needed, or what the actions return. For a destructive multi-action tool this leaves substantial behavioral gaps.

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?

Two short sentences with the action list front-loaded and no filler. Efficient, though brevity here borders on under-specification for a 14-parameter tool.

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 destructive, 14-parameter, four-action tool with 21% schema coverage and no output schema, the description is far too thin. It omits per-action parameter requirements and any behavioral context an agent would need to invoke log/solve correctly.

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?

Schema coverage is only 21% across 14 parameters, so the description carries the burden of compensation and fails to. It documents project (name or id) but says nothing about title, summary, severity, description, key_insight, code_snippet, problem_id, component_id, or winning_attempt_id – notably which parameters are required per action. The action enum is merely repeated from the schema.

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?

"Manage problems" is a plausible but vague verb+resource pairing, and the enumerated actions (log, list, solve, get_tree) largely restate the enum already present in the schema. It never distinguishes this tool from siblings like log_learning or todo, so an agent must infer scope. Adequate but with a clear differentiation gap.

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 only guidance is the write precondition ("requires project"), which is a prerequisite rather than a routing rule. There is no statement of when to use this tool versus log_learning/log_change/todo, and no exclusions or alternatives named. Usage is left entirely to inference.

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