get_firm_user_mappings

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

No annotations are provided. The description does not mention that this is a read-only operation, nor does it disclose any behavior like pagination, limits, or sorting. For a list operation targeting a potentially large number of records, this is insufficient.

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 with no extra words. It is clear and front-loaded with the action and resource.

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 has no parameters and an output schema exists, the description is minimally adequate. However, it does not explain the concept of 'user mappings' or what the output contains, relying on the schema. For a simple listing, this is acceptable but could be slightly improved.

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 no parameters, and schema description coverage is 100% (since there are none). Baseline is 4 for zero parameters; the description does not add or need to add parameter details.

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 verb 'list', the resource 'user mappings', and the scope 'for this firm'. It distinguishes from sibling 'get_firm_user_mapping' which implies singular retrieval.

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?

No guidance on when to use this vs alternative tools. Sibling 'get_firm_user_mapping' exists but is not mentioned. No context about prerequisites or scenarios.

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