Track time

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

With only readOnlyHint=false in annotations, the description carries the full burden of behavioral disclosure. It clearly reveals that hours are converted to minutes, the service is derived from the task when absent, and the person is resolved from the authenticated caller despite a shared server token. This is specific and valuable transparency.

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 sentences, each earning its place: the first states the action, the second explains the critical unit conversion, and the third clarifies lookup defaults and authentication behavior. It is dense without being bloated, and the essential action is front-loaded.

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 8-parameter tool with no output schema, the description covers the core call flow well: what to log, how units are handled, which IDs can be omitted, and how resolution works. It does not describe the return value or what happens when conflicting inputs like hours and minutes are both supplied, but these are minor gaps given how much is already explained.

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 88%, so the schema already documents most parameters. The description adds real value by explaining the hours-to-minutes conversion, the distinction between service and task, and the fallback resolution behavior for serviceId and personId. It does not explain every edge case, such as providing both hours and minutes, but it meaningfully supplements 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?

The description opens with a specific verb and resource: 'Log a time entry.' It goes beyond the title by explaining the key behavior that makes this tool distinct from generic create/list tools: it avoids manual lookups and handles conversions, making the intent unmistakable.

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 gives clear practical context: service can be omitted and is resolved from the task, person can be omitted and is resolved from the caller. This tells an agent when it can avoid passing certain parameters, though it does not explicitly name alternatives or state when not to use the tool.

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