get_user_timelogs

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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the description earns credit for the extras it adds: inclusive date-boundary semantics and a warning that the dedicated route may be unavailable on older instances, which tells the agent to be ready for a degraded path. It still says nothing about pagination or result size behavior.

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?

Two short sentences, front-loaded with the core purpose and followed by the operational caveat. No filler, no repetition of the tool name or schema.

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?

With 9 parameters, nested offset objects, cursoring fields and a 33% schema coverage rate, this is a complex tool whose description is far too thin. An output schema exists so return values need not be explained, but pagination mechanics and the meaning of detail modes are unaddressed anywhere the agent can easily find them.

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 only 33% across 9 parameters, so the description must carry more weight than it does. It clarifies the from/to inclusive-range semantics, but limit, offset, detail, previous_page, text_offsets and section_offsets are left entirely to the schema, several of them undocumented there too.

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?

States a specific verb and resource (read user time logs) plus the scope (inclusive calendar date range), which implicitly separates it from the sibling get_card_timelogs and get_timesheet. It never names an alternative explicitly, so sibling differentiation is left to inference.

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?

There is no when-to-use guidance and no comparison against the closely related get_card_timelogs or get_timesheet tools. The availability note about older instances is a runtime caveat, not selection guidance.

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