read_employee_salary

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

With no annotations provided, the description carries the behavioral disclosure burden. 'Read' implies a non-mutating operation, and 'latest rows' suggests ordering by recency, but the description does not reveal limits on result size, pagination behavior, or any other side effects or constraints.

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 two short sentences with no filler. The primary action is front-loaded, and the secondary sentence provides useful usage guidance without redundancy.

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 tool with one optional parameter and an output schema, the description is reasonably complete. However, it leaves the limit parameter semantics and the relationship to query_employee_salary implicit, so an agent must infer when this tool is the right choice.

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 does not explicitly explain the 'limit' parameter or how it relates to 'latest rows.' The phrase 'Keep the result small' indirectly implies limiting output, but it does not add clear parameter-level meaning beyond the schema's title and default.

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 the action ('Read') and the resource ('employee_salary'), and narrows the scope to 'latest rows,' which helps distinguish it from the more general query_employee_salary sibling. However, it does not explicitly name or contrast the sibling tools, so it stops short of full differentiation.

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 instruction 'Keep the result small for LLM use' gives clear practical context for how the tool should be invoked. It does not explicitly state when to choose this tool over query_employee_salary or get_employee_salary_schema, so there is no exclusion guidance.

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