list_applicants

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It only states the action and return format, but does not explicitly mention that this is a read-only operation, any authentication requirements, or behavioral constraints like sorting or filtering beyond the email parameter.

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 concise and well-structured, with a clear purpose line, an Args section listing each parameter, and a Returns line. Every sentence earns its place and the information is 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?

The tool is simple with 3 optional parameters, and the description covers the purpose, parameters, and return type. However, it lacks usage guidance and does not detail the structure of the metadata or any constraints on the applicants returned, leaving some ambiguity for an agent.

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 descriptions are completely absent (0% coverage), but the description thoroughly explains each parameter: 'email: Optional email address to filter by', 'limit: Maximum number of results (default: 100)', 'offset: Offset for pagination (default: 0)'. This adds full meaning beyond the schema's property names and types.

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 'List rental applicants from Buildium' with a specific verb and resource, making the primary action unambiguous. However, it does not explicitly differentiate from sibling tools like get_applicant or list_applicant_applications, though the resource name helps distinguish it.

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 get_applicant for a single applicant or list_applicant_applications for applications. It simply states the action and parameter details without any context about use cases or exclusions.

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