get_conglomerate_constituents

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

With no annotations, the description carries full burden. It discloses output details (slug and price returns for multiple periods) and contrasts with the conglomerates tab. However, it does not mention error handling, data freshness, or pagination, which could be expected.

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 front-load purpose and parameter guidance, followed by output details and contrast. Every sentence adds value with no extraneous text.

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 simple one-parameter tool with no output schema or annotations, the description covers purpose, parameter source, and output format sufficiently. Minor gaps like error handling or data type for returns do not detract from overall completeness.

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 description must compensate. It provides meaningful context for tjiid by specifying its origin from get_markets, which aids correct invocation. Yet it could further clarify the property's meaning (e.g., 'conglomerate group ID').

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 the verb 'Get' and clearly identifies the resource as 'constituent companies of a conglomerate group'. It also differentiates from siblings by referencing the specific source of the tjiid ('from get_markets({ tab: 'conglomerates' })') and contrasting output with the conglomerates tab's ROE 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 explains when to use (after get_markets for a conglomerate) but does not state when not to use or explicitly name alternatives like get_sector_constituents. The contrast with get_markets' tab provides context but lacks explicit redirection.

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