get_sector_performance

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only states a basic action without detailing data source, frequency, time period, or limitations. This offers minimal insight beyond what the tool name implies.

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 a single, focused sentence with no redundant words. It is appropriately sized for a simple read operation, though slightly under-specified in terms of content.

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?

With no output schema, the description does not explain return values or data structure, but the tool's purpose is fairly self-explanatory. Additional context on which sectors are included or what metrics are shown would improve completeness, but it is adequate for a basic snapshot 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 schema covers the single parameter (date) with a clear description (YYYY-MM-DD, optional, defaults to latest), providing 100% coverage. The tool description adds no additional parameter context, but the schema fully compensates.

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') and resource ('sector performance snapshot'), clearly identifying the tool's function. It distinguishes from sibling tools that focus on individual stocks or indicators, though it could be more explicit about what constitutes 'sector performance'.

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 provides no guidance on when to use this tool versus alternatives like get_market_gainers or get_sp500_constituents. There is no mention of scenarios where this tool is preferable or any exclusionary language.

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