get_sector_constituents

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

With no annotations, the description carries the full burden. It details the output including slug, weights, and returns for multiple periods. While it implies read-only behavior, it does not explicitly state side effects or rate limits, but the comprehensive output description adds significant transparency.

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?

Two sentences efficiently cover the core function, input source, and detailed output. No unnecessary words; every sentence earns its place.

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?

For a single-parameter tool with no output schema, the description is remarkably complete. It explains input derivation and enumerates all return fields, ensuring the agent understands what to expect.

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 adds meaning to the lone parameter tjiid by specifying its source ('from get_markets({ tab: 'niche' })'), which is not evident from the schema alone. Given 0% schema coverage, this contextual guidance is valuable.

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 ('Get all constituent companies') and resource ('TJI niche sector index'), clearly differentiating from the sibling tool 'get_conglomerate_constituents' via the 'niche' qualifier.

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?

It explicitly instructs to use tjiid from get_markets with tab 'niche', providing a clear prerequisite and context. However, it does not state when not to use this tool or mention sibling alternatives beyond the implicit differentiation.

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