getStaff

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

No annotations are provided, so the description must carry the full burden. It only says 'Get all staff members with optional filters', which adds no details about permissions, filtering semantics, pagination, or response characteristics. The behavior is largely assumed from the tool name.

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, eight words, and immediately communicates the core function. No wasted words or repetition of schema details.

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 read-only lookup with no output schema, the description is adequate but leaves gaps. It doesn't explain filter semantics, available filter options, or any restrictions. Since parameters are well-defined in the schema, this is minimally viable but not rich.

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 each parameter has its own description (e.g., 'Filters to apply', 'Specific staff IDs to retrieve'). The tool description only adds the generic phrase 'optional filters', which is redundant with the schema and doesn't clarify how filters are combined or formatted.

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 resource (staff members) and action (get all), with optional filters. It is distinguishable from sibling tools like getStaffAppointments and getTeacherSchedule, though it doesn't explicitly contrast them.

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 this is a read-only listing tool, but provides no explicit guidance on when to use it versus alternatives (e.g., getTeacherSchedule for schedules). It lacks any exclusions or context about filter usage.

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