compare_smallcases

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

No annotations are provided, so the description must fully disclose behavior. It states 'compare' but does not clarify whether the operation is read-only, safe, or requires any authentication. No mention of side effects or return format.

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 short and front-loaded with the core purpose in a single sentence, followed by a clear parameter explanation. Every word earns its place, though the SCID example could be integrated more efficiently.

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 has no output schema, yet the description does not describe the format of the comparison results. While it mentions 'returns, risk, minimum investment', it lacks details on how the output is structured (e.g., table, JSON). This is a significant gap for a comparison tool.

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 coverage is 0%, so the description must compensate. It explains 'scids' as a list of 2-5 SCIDs with an example, adding meaning beyond the bare 'array of strings' type. However, it does not define what a SCID is or where to obtain them.

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 tool compares 2-5 smallcases side by side, specifying metrics (returns, risk, minimum investment) and the number of smallcases. This clearly distinguishes it from sibling tools like get_smallcase (single smallcase) or search_smallcases (searching).

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 implies use for comparing multiple smallcases but does not explicitly state when to use this tool versus alternatives like search_smallcases or get_smallcase. No guidance on prerequisites or when to avoid this tool.

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