get_total_worklogs

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It states 'Get' which implies a read-only operation, but it does not explicitly confirm no side effects, does not mention permissions, rate limits, or any other behavioral context beyond the bare action.

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 extremely concise: a one-sentence summary plus an Args list for the single parameter. Every element is useful and front-loaded, with no filler.

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 one-parameter tool with an output schema, the description is minimally viable. However, it leaves ambiguities such as the unit of the total (seconds? hours?), whether it aggregates across all issues, and whether any filters apply. It is not rich enough to fully understand the tool's behavior without additional assumptions.

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 0% since the schema properties lack descriptions. The description compensates by explaining project_id as 'The UUID identifier of the project to get total worklogs for', adding type specificity and purpose beyond the schema's bare 'string' type.

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 'Get total logged time for a project', which is a specific verb+resource combination. The scope ('total' and 'project') distinguishes it from sibling tools like get_issue_worklogs that operate at the issue level.

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 is provided on when to use this tool versus alternatives, such as get_issue_worklogs or create_worklog. There is no mention of prerequisites, typical scenarios, or exclusions.

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