b24_task_elapsed_add

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

Annotations already indicate readOnlyHint=false (mutation) and destructiveHint=false. Description adds 'Log time' which is consistent but provides no additional behavioral context beyond what schema and annotations offer. No mention of side effects, rate limits, or auth requirements.

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?

Very short (one sentence plus parenthetical), front-loads the action. Minimal but efficient. Could include more structure without being verbose.

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 5 parameters, required=2, and output schema exists, the description is minimal. It states the return value ('entry id') but doesn't explain output format or additional context. Adequate but could be improved.

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 parameters are well-documented in schema. The tool description adds no extra meaning for parameters. Baseline score of 3 fits since description doesn't need to compensate.

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?

Description clearly states the action 'Log time spent on a task' and mentions the underlying API method 'task.elapseditem.add' and that it returns the entry id. This distinguishes it from sibling task tools like b24_task_comment_add or b24_task_add.

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 tool vs alternatives. Doesn't mention prerequisites like task existence, permissions, or when not to use it (e.g., for creating tasks vs logging time). Sibling tools exist but no differentiation.

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