query_employee_salary

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

With no annotations provided, the description carries the full burden of disclosing behavior. It explicitly states the operation is read-only and limits input to SELECT statements, which is the most important safety behavior. It does not detail output formatting or query limits, but the available output schema helps cover return-value expectations.

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. It front-loads the core action and constraint immediately, and every sentence adds meaningful guidance.

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 single-parameter tool with an output schema, the description is largely sufficient: it names the target table, restricts the query type, and clarifies read-only intent. It could be more complete by mentioning sibling-tool usage or query limits, but those are secondary for correct invocation.

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 input schema provides only the parameter name 'sql' with no description, so schema coverage is 0%. The description compensates by clarifying that the sql parameter is a SQL query, must target the employee_salary table, and must be a SELECT statement. This gives the agent enough semantic grounding to construct the argument.

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 verb and resource: run a read-only SQL query against the employee_salary table. It also specifies that only SELECT statements are allowed, which gives concrete scope. However, it does not explicitly differentiate itself from sibling tools like read_employee_salary or get_employee_salary_schema.

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 implies this tool is for running ad-hoc read-only SQL queries against the employee_salary table. It provides a meaningful constraint ('Only SELECT statements are allowed') but gives no explicit guidance on when to choose this over read_employee_salary or get_employee_salary_schema.

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