get_hourly_rates

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

With no annotations provided, the description carries full behavioral burden. It discloses the return payload fields (name, amount, currency, customer, active status) and confirms pagination behavior. It does not explicitly state read-only semantics or auth requirements, but for a 'get' tool with this level of detail, it is fairly transparent. The lack of explicit safety info keeps it from a 5.

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 three tightly written sentences with no fluff. Purpose is front-loaded, return fields follow, and usage notes come last. Every sentence contributes value and the structure is efficient for cognitive parsing.

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 simple read-only tool with 3 optional parameters, the description covers the essential calling information: what it returns, how to filter, and that results are paginated. Since the schema already explains pageSize and pageNumber defaults, the description is sufficiently complete. It only lacks a note on when to prefer this over get_contract_hourly_rates, which is a minor gap.

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 100%, so all three parameters already have clear descriptions. The tool description adds no new semantic detail beyond restating 'searchText' as a filter and mentioning pagination, which the schema already covers. This aligns with the baseline of 3 for high-coverage schemas.

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 starts with a clear verb+resource: 'Get hourly rates defined in Timelog.' It lists the exact return fields (rate name, amount, currency, customer, active status) and mentions filtering and pagination. This clearly distinguishes it from the sibling get_contract_hourly_rates by specifying the source context ('defined in Timelog').

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 gives some usage hints: 'Use searchText to filter by name' and 'Results are paginated.' However, it does not explicitly explain when to use this tool versus get_contract_hourly_rates, a closely named sibling. There is no when-not or alternative routing. The guidance is implied at best, not explicit.

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