hcm_search_time_records

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

The readOnlyHint annotation already marks the tool as safe/read-only, and the description's 'Search' verb aligns with that. The description adds minor context by identifying the Fusion timeRecords abstraction, but it does not disclose pagination, result limits, finder requirements, or other behavioral traits beyond the annotation.

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 short and front-loaded, but it is under-specified for a tool with four undocumented parameters and no output schema. It is concise to the point of omitting useful structure, so it only partially satisfies the conciseness and appropriate-sizing criteria.

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 no output schema, 0% parameter coverage, four optional parameters, and no usage guidance, the description is far from sufficient for an agent to select and invoke this tool correctly among dozens of HCM siblings. The only context provided is the resource name and read-only intent.

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 0%, and the description provides no explanation of q, limit, finder, or offset. An agent cannot infer what search query syntax is expected, how finders relate to q, or what defaults apply for limit and offset, making the parameter semantics effectively undocumented.

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 states a specific action ('Search') and resource ('time records'), with the added context of the underlying Fusion API object ('Fusion timeRecords'). It is clearly a list/search operation, distinct from sibling hcm_get_time_record which implies fetching a single record, though it does not explicitly name the sibling.

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 search tool versus alternatives like hcm_get_time_record or hcm_submit_time_card. The description implies a search use case but gives no context on what inputs distinguish it or when a more specific getter would be preferable.

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