passgage_list_payrolls

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

No annotations exist, so the description must carry the burden of behavioral transparency. It only mentions optional filtering and pagination, which is already reflected in the schema. It does not describe response format, authentication requirements, defaults beyond schema, or any side effects. This is a significant gap for a read operation.

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 sentence, immediately states the action, and contains no redundant information. It is efficiently front-loaded.

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 no output schema and no annotations, the description should provide more context about what the tool returns or how to interpret the results. It does not, and the only behavioral details are generic. For a list endpoint, this is minimal but insufficient for fully autonomous use.

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?

All three parameters are documented in the schema with descriptions and constraints. The description's reference to filtering and pagination aligns with the schema but adds no additional semantics beyond what is already present, so baseline 3 is appropriate.

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 tool lists payrolls, which distinguishes it from sibling tools like passgage_get_payroll or passgage_create_payroll. The mention of filtering and pagination adds useful scope.

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 usage for retrieving payroll records, but does not explicitly state when to prefer this over related tools, nor does it provide alternative tool references or exclusions. The 'optional' nature of filtering is noted but not elaborated.

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