get_sector_constituents

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It details the output format including each company's slug, market-cap weight, equal weight, and multiple price returns, enabling the agent to anticipate results.

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 concise with just two sentences: the first states the core purpose, the second explains parameter sourcing and return data. Every word adds value 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?

Despite no output schema, the description fully covers the single parameter and comprehensively lists the output fields, including how slugs can be used with other tools. This makes the tool self-contained and easy to invoke.

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 description coverage is 0%, but the description adds substantial meaning: it explains that 'tjiid' comes from get_markets({ tab: 'niche' }) and is required, far exceeding the schema's minimal type definition.

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's purpose: 'Get all constituent companies of a TJI niche sector index.' It specifies the resource (TJI niche sector index) and action (get constituents), distinguishing it from sibling tools like get_conglomerate_constituents and get_markets.

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 explicitly instructs how to obtain the required parameter: 'Pass the tjiid from get_markets({ tab: 'niche' }).' This provides clear usage context, though it does not explicitly mention when not to use the tool.

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