getTimeEntryActivities

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

The annotation readOnlyHint=true already declares this a read-only operation, so that is covered. However, the description adds no further behavioral context—no mention of output format, pagination, or the nature of 'activities'. With annotations present, the description provides minimal added value.

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 short, which is technically concise, but it omits essential information. It is under-specified rather than appropriately concise, lacking any detail beyond the basic action.

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 tool has only one parameter, no output schema, and sits among many similar siblings, the description should clarify what 'time entry activities' are and when to use this tool. It provides none of that, leaving the agent without enough context to select or invoke it correctly.

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 schema documents a single 'format' parameter with an enum of json and xml, but the description does not mention it. With schema description coverage at 0%, the description fails to compensate by explaining the parameter's meaning or usage.

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 'List time entry activities' states a clear verb and resource, but it does not distinguish what 'activities' means relative to the sibling 'getTimeEntries'. While it names the operation, it is vague about the specific entity being listed.

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 like getTimeEntries or other listing tools. There is no mention of context, exclusions, or prerequisites, leaving the agent to guess.

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