Teamwork: log time

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention that at least one of taskId or projectId is required (a critical constraint visible only in the schema), whether the operation is reversible/editable, or the authentication/permission context. For a mutation tool that creates records, this is a significant transparency gap.

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?

A single, efficient sentence that states the verb, resource, and scope with zero waste. The core purpose is front-loaded and immediately understandable.

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 6 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain the critical requirement of providing taskId or projectId (only visible in the schema description for projectId), doesn't describe what the tool returns, and doesn't clarify the relationship between the two target types. With 6 parameters, an agent needs substantially more context to call this 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?

The input schema covers parameter descriptions at 83% coverage (all parameters are described except isBillable which only has type boolean). The description itself adds minimal parameter context—it doesn't clarify the taskId/projectId relationship or the default date behavior beyond what the schema's 'default today' already states. The description adds some value by noting both task and project targets, but doesn't fully compensate for the missing isBillable semantics.

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 identifies the action (log a time entry) and the target resources (task or project), which accurately distinguishes it from typical project-management tools. However, it doesn't explicitly differentiate from sibling tools like task management or project creation tools, though the timesheet specificity provides reasonable clarity.

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 description implies usage by stating the core function but provides no explicit guidance on when to use this tool versus alternatives. It doesn't mention that taskId or projectId is required, nor does it address scenarios like logging time against both a task and project, or time-logging best practices. There's no exclusions or alternative tool routing.

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