analytics_rh

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

No annotations provided, so description carries full burden. Discloses constraints: SELECT only, no CTEs/semicolons/comments, and governance validation. Does not mention rate limits or authentication, but adds valuable behavioral context.

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?

Every sentence serves a purpose: action, usage, schema, constraints. No wasted words; front-loaded with the core function.

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?

Covers purpose, usage, SQL details, and constraints. Output schema exists, so return values need not be described. Could explicitly state no side effects, but overall complete for a SQL query tool.

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 coverage is 0%, but description fully compensates by detailing the required SQL content, exact table and columns, and formatting constraints. Adds critical meaning beyond the generic schema title.

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?

Specific verb 'Executa' and resource 'consulta analítica SELECT no data warehouse (BigQuery)'. Clearly distinguishes from sibling tools like 'aprovar_ajuste' (approvals) and 'consultar_batidas' (time tracking).

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?

Explicit use cases for aggregate queries (horas extras, atrasos, batidas incompletas) and specifies the table and columns. Lacks explicit when-not-to-use or alternative pointers, but sibling context helps.

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