listAutomationsPeople

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

Annotations are absent, so the description bears the full burden. It discloses a key behavioral constraint: 'Restricted - Registered Systems Only' and requires FUB_SYSTEM + FUB_SYSTEM_KEY. However, it does not mention pagination, response format, or side effects, offering only minimal transparency beyond the schema.

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 two short sentences. The first states the purpose, and the second provides essential access restrictions. Both sentences earn their place, and there is no wasted text.

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 list operation with optional filters, the description plus full schema coverage is minimally adequate. It names the purpose and a critical restriction, but offers no output description and no comparison to similar tools. It is not severely lacking, but does not go beyond the essential minimum.

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%, so the description does not need to explain parameters. The description adds no extra meaning beyond the schema's detailed parameter descriptions (limit, offset, personId, automationId). Baseline 3 applies.

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's function: 'List people in Automations 2.0 automations.' It uses a specific verb ('List') and resource ('people in automations'), and distinguishes it from siblings like listAutomations (which lists automations) and getAutomationPerson (which gets a single person in an automation).

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 provides no guidance on when to use this tool versus alternatives such as getAutomationPerson or listActionPlansPeople. It only mentions a restriction, but no explicit context or exclusions. This falls under 'no guidance'.

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