get_exit_passes

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

No annotations are provided, so the description carries the full burden. It merely states the purpose and does not disclose behavioral traits such as pagination, status filtering, or whether results are read-only. The schema implies pagination and status, but the description adds no behavioral context beyond the action.

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, concise sentence that states the action, resource, and scope without redundant text. It is front-loaded and efficiently communicates the essential purpose.

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?

Given the tool's simplicity and the rich parameter schema, the description is sufficiently complete. It lacks an output schema but 'List' naturally implies a list of exit passes, and the schema covers all parameters. A slightly more detailed mention of pagination or status could improve it, but it is adequate.

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 input schema has 100% description coverage for all four parameters, so the baseline is 3. The description adds no extra parameter meaning beyond what the schema already provides, only associating the flat_id concept.

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 uses a specific verb 'List' with a clear resource 'exit passes' and adds scope 'for a flat'. It also clarifies what exit passes are ('material movement out of society'), distinguishing this tool from other listing tools.

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 clearly indicates the tool is for listing exit passes related to a flat, providing context for when to use it. It doesn't explicitly name alternatives or exclusions, but the context is clear enough given the tool name and sibling list.

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