myob_employee_list

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

With no annotations to lean on, the description carries the full burden of disclosure. It only states 'List employees' and gives no information about pagination, filtering, authentication, rate limits, or whether the operation is read-only, which is a significant gap for a tool with no other metadata.

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 short but under-specified. Being concise does not compensate for the lack of useful information; this is closer to an empty shell than a well-structured description.

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 has output schema, but the description gives no context about when to call it, what the output contains, or how the parameters affect results. This is inadequate even for a simple list tool, especially given the abundance of sibling tools.

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 0%, and the description adds no explanatory value for the three parameters ('top', 'filter', 'business_id'). The agent is left with only names and defaults, which is insufficient for correct invocation.

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 'List employees' clearly identifies the action (list) and the resource (employees). It distinguishes from sibling list tools by resource name, but doesn't explicitly address alternatives or scope, so it stops short of a 5.

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 like myob_entity_list or other list-specific tools. There are no prerequisites, exclusions, or context clues to direct the agent.

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