solidtime_tasks

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true and idempotentHint=true, so the safety profile is carried structurally. The description adds the confirm gate for writes, which is genuinely useful behavioral context, but it does not say what delete destroys (and whether it cascades), nor how the dry-run response differs from the confirmed one.

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?

Three short sentences with no padding, and the action list is front-loaded. However the telegraphic style means the sentence about estimated_time repeats the schema, while more consequential information (which parameters each action requires) is omitted entirely.

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 9-parameter destructive multi-action tool with no output schema, the description is too thin: an agent cannot tell which fields are mandatory per action or what list returns. Annotations do cover mutability and the confirm hint covers the write gate, which keeps this from being inadequate, but the parameter-to-action mapping is a real gap.

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 description coverage is only 22% across 9 parameters, and the description compensates for exactly one of them: "estimated_time is the task estimate in seconds," which merely repeats the schema's own parameter description. It leaves the ambiguous done vs is_done pair, name, task_id and project_id unexplained, so most of the coverage gap remains unaddressed.

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?

"Tasks. action list, create, update, delete." identifies the resource and enumerates the four operations, so the agent knows this is a task CRUD tool. But it is largely a restatement of the action enum in the schema and says nothing about what a task is scoped to (project, organization) or how listing behaves, so the purpose is adequate rather than specific.

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 on when to use this versus any alternative, and no per-action preconditions (e.g. create needs name and project_id, update/delete need task_id). The only procedural hint is "Writes need confirm," which signals the dry-run-first flow but does not tell the agent which action to pick in a given situation.

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