time_tracking

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

With no annotations, the description carries the burden for behavioral disclosure. It only lists high-level functions without detailing behavioral traits like mutability, idempotency, rate limits, or side effects. The enum descriptions in the schema provide some action-level context, but the description itself adds little beyond summarizing the schema.

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?

The description is a single concise sentence that front-loads the main capabilities. However, it could be more structured by grouping actions or providing a brief example. Overall, it is appropriately sized but could earn its place with more precision.

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?

Given the tool's complexity (12 parameters, 8 enumeration actions, no output schema), the description is severely incomplete. It does not explain return values, pagination, error handling, or usage patterns for different actions. The agent is left with insufficient context to use the tool effectively.

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 100%, so each parameter's purpose is already documented. The description adds no new meaning beyond restating the actions listed in the action enum descriptions. It does not explain parameter interdependencies, default behaviors, or format constraints beyond what the schema provides.

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 states the tool covers time tracking, work items, and reports, with specific actions like 'log time', 'manage entries', 'generate reports'. However, it does not distinguish it from sibling tools like 'analytics' (which may also generate reports) or 'issues' (which may have time tracking).

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 provides no guidance on when to use this tool vs alternatives. It does not specify prerequisites, when not to use it, or mention sibling tools. The agent must infer usage from the broad description alone.

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