Buildium Created Fixtures

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, and the description is consistent. It adds a non-obvious side effect: the tool appends to created-records.log, which is beyond the annotations. It also explains the purpose of that side effect (cleanup after the process), providing valuable behavioral disclosure.

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 sentences, front-loaded with the core purpose, and immediately follows with the critical usage context and side-effect. No fluff or redundancy; every sentence earns its place.

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?

With no parameters, an output schema present, and annotations covering safety, the description adds the essential context about fixtures mode, permitted operations, and log behavior. The agent has everything needed to decide when to call this tool and what to expect.

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?

The tool has zero parameters, so schema coverage is trivially 100%. The description adds no parameter-specific detail, but none is needed. The baseline for 0 params is 4, and the description fully suffices; there is no missing parameter meaning to compensate for.

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 states a specific verb ('List') and resource ('records created during this session'), and clarifies the grouping by collection. It clearly differentiates from siblings like buildium_list_tenants or buildium_list_leases by focusing on session-created fixtures, which is a distinct scope.

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 explicitly states when this tool is relevant: 'These are the only records that updates and deletes are permitted against in fixtures mode.' This tells the agent when to consult this list before performing updates/deletes, and implicitly that other tools are for different operations. It also mentions the log append for cleanup, adding practical context.

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