get_time_tracking

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

Because no annotations are present, the description must carry the full burden of behavioral disclosure. It only states the basic action and does not clarify permissions, return format, or behavior when no time tracking data exists. This exceeds minimal transparency but falls short of a safe, informative profile.

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, short sentence with no redundant words, making it easy to parse. It is appropriately concise for a simple getter, though additional detail could be added without harming structure.

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 absence of an output schema and annotations, the description should explain what 'time tracking info' includes and how it relates to sibling tools like get_worklogs. It fails to provide this context, leaving the return value and tool boundaries unclear.

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 single parameter issueKey is self-explanatory, and the description's phrase 'for an issue' adds minimal semantic value. With 0% schema description coverage, the description should compensate with details like format or examples, but it does not.

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 action ('Get') and the resource ('time tracking info'), with an explicit object ('for an issue'). This distinguishes it from related tools like get_issue and get_worklogs, though the exact scope of 'time tracking info' is left vague.

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 versus alternatives such as get_worklogs or add_worklog. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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