Get client simulations

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. The description adds the domain context 'mortgage simulations' but does not disclose any additional behavioral traits such as pagination, ordering, or error handling. It is consistent with annotations, neither contradicting nor adding significant value.

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 with no redundant words. It conveys the purpose effectively without unnecessary elaboration.

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 simplicity of the tool (one parameter, no output schema), the description provides the basic purpose but lacks information about the return format or any details about what the list contains (e.g., simulation fields, statuses). The presence of annotations reduces the burden, but the description is still minimal for an agent to fully understand expected inputs and outputs.

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 schema has one parameter 'uuid' with no description (0% coverage). The description mentions 'a client's' which hints that the uuid identifies the client, but it does not explicitly state that the uuid parameter is the client's UUID or how it should be formatted. The description fails to compensate for the lack of schema documentation.

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' and identifies the resource as 'a client's mortgage simulations.' This clearly differentiates from sibling tools like get_simulation (singular) and calc_simulation, indicating this retrieves the collection of simulations for a specific client.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description implies it is for listing simulations but does not mention get_simulation for fetching a single simulation or any preconditions like having a client UUID. The usage context is only implicit.

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