listAutomationsPeople

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

With no annotations present, the description must fully disclose behavior. It adds the auth restriction, which is helpful, but does not describe pagination behavior, read-only nature, or whether all results are returned without filters. The schema provides parameter descriptions, so the description adds only the auth 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?

The description consists of two clear sentences: one stating the purpose, one for the restriction. No unnecessary words; highly efficient.

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 simple list tool with 4 optional filter parameters and no output schema, the description is largely sufficient. It lacks details about response structure or behavior when no filters are applied, but given the simplicity, it is adequate.

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 coverage is 100%, with each parameter having a basic description. The tool description does not add any additional parameter-specific information beyond what the schema already provides, 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 tool name 'listAutomationsPeople' combined with the description 'List people in Automations 2.0 automations' clearly states the action and resource. It distinguishes from siblings like 'listPeople' (lists all people) and 'listAutomations' (lists automations).

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 mentions the restriction 'requires FUB_SYSTEM + FUB_SYSTEM_KEY', which informs when the tool is usable. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., versus 'listPeople' for general people listing).

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