solidtime_time_entry_create

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

Annotations already declare non-readonly, non-destructive, non-idempotent, open-world, so the safety profile is partly covered. The description usefully adds two behaviors annotations cannot express: omitting end leaves an open/running entry, and the write is a dry-run unless confirm is supplied. It still omits what the dry-run returns, whether a duplicate start is rejected, and any rate or permission constraints.

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?

Four telegraphic sentences, each carrying a distinct actionable fact, with the core operation front-loaded. The fragmentary style is efficient rather than padded, though the shorthand ('member_id is a membership id') is thinner than the schema's own wording and adds little.

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 an 11-parameter mutation with no output schema and partial schema coverage, the description covers the two highest-risk behaviors (dry-run gate, open-ended timer) but leaves the agent guessing about most field semantics and the response shape. Adequate as a minimum, not sufficient for a tool of this complexity.

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 36% across 11 parameters, so the description needs to compensate and largely does not. It restates what the schema already says about member_id, confirm and end, but never explains billable, type, tags, project_id, task_id, description, or organization_id, leaving eight parameters undocumented in both places.

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?

States a concrete verb and resource ('Create a time entry') plus the underlying POST path, so the agent knows exactly what the tool does. It does not, however, differentiate itself from adjacent siblings like solidtime_timer_start, which the 'omit end to start a timer' clause actually brings it closer to.

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?

Gives useful conditional guidance on two parameters (omit end for a running timer, omit confirm for a dry-run), which implicitly tells the agent how to use the tool in two modes. It never says when to prefer this over solidtime_timer_start or solidtime_time_entry_update, and no prerequisites are stated.

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