Folha de pagamento (RH)

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

No annotations provided, so description carries full burden. It discloses that without employeeId no personal data is returned, and with employeeId sensitive data is returned. Does not mention read-only nature or side effects, but the core behavioral trait (data sensitivity) is well communicated. Could add a note about being read-only.

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?

Two sentences, minimal words. Front-loaded: first sentence states tool, second explains behavior. No redundancy, every sentence adds value.

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?

Given single parameter, no output schema, and no annotations, the description is complete. It fully explains both modes and data sensitivity. No missing information for selecting and invoking the tool correctly.

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 already covers employeeId as optional sensitive data. Description adds meaning by explaining the different outputs based on presence/absence of this parameter, which goes beyond the schema. Baseline 3 due to 100% coverage, but extra context raises score.

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?

Description clearly states 'Demonstrativo de pagamento (RH)' and distinguishes two modes: without employeeId returns types of salary changes (no personal data), with employeeId returns employee statement (sensitive personal data). It is a specific verb-resource pair that differentiates from sibling tools.

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?

Explicitly tells when to use each mode: 'Sem employeeId, retorna os tipos de alteração salarial ... Com employeeId, retorna o demonstrativo do funcionário'. Provides clear context and warns about sensitive data.

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