get_market_regime

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

Discloses that data reflects institutional positions and should not be interpreted as intent, which is helpful behavioral context beyond mere operation. No annotations exist, so description compensates well.

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?

Description is concise: two sentences plus an Args/Returns section. No wasted words, clearly front-loaded with key purpose and caveat.

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 simple schema (1 param, no output schema, no enums), the description provides enough context: purpose, caveat, and return example. However, lacks details on quarter format or sources but sufficient for a straightforward 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?

The description mentions 'quarter: quarter code' which adds minimal meaning beyond the schema (which has no description). With 0% schema coverage, the description partially compensates but lacks detail on format or valid quarter codes.

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?

Description states tool returns institutional regime snapshot for a quarter, with clear verb 'Return' and resource 'institutional regime snapshot'. It distinguishes itself from siblings like list_quarters or search_managers by focusing on regime state data.

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?

Description explicitly says 'Research data only' and warns against inferring manager intent, which guides appropriate use. However, it does not explicitly state when to use this vs alternatives or exclude cases.

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