get_all_salary_slips

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

No annotations are provided, so the description must disclose behavioral traits. The description only states 'Get all salary slip files', which implies a read operation, but does not mention whether results are paginated, require authentication, or what a 'salary slip file' entails. The lack of detail on safety (e.g., no mutation is obvious but not confirmed) or limits is problematic.

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 a single short sentence (4 words), which is concise but overly terse. It lacks structure (e.g., no phrase break or additional context) and may be too sparse to be helpful. A slightly longer description with more context would be more effective.

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?

The tool handles sensitive salary slip data and zero parameters, yet the description fails to explain what 'get all salary slip files' means in practice (e.g., returns a list of files? file contents? any implicit filtering?). No output schema exists to fill gaps, making the description insufficient for an agent to predict behavior.

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?

With zero parameters and schema coverage at 100%, the baseline is 3. The description adds no additional parameter meaning beyond the schema, so it meets the minimum but does not improve understanding.

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 ('Get') and resource ('all salary slip files'), showing retrieval of multiple files. It is specific enough to distinguish from siblings like 'get_file_download_url' (single file) and 'get_person_detail' (non-file), but lacks detail on output format (e.g., list of file names or contents).

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?

No guidance on when to use this tool versus alternatives. Siblings like 'get_file_download_url' or 'list_people' are conceptually different, but the description does not specify context (e.g., 'Use this to list all available salary slips before downloading one'). The purpose is implied but not clarified.

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