Analyze portfolio allocation and concentration

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

With no annotations, the description carries the full burden and covers it well: deterministic not estimated, sector classification sourced from NSE macro-economic data rather than user input, and unclassified instruments are reported/counted rather than guessed. This is strong behavioral disclosure.

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?

Every clause earns its place: deterministic behavior, classification source, unclassified handling, and optional target comparison are all functional for selection and invocation. Information is front-loaded with the core computation.

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 tool with no output schema, the description lists the computed metrics and drift comparison, which is reasonably complete. However, the exact output shape/format is not specified, and given no annotations, slightly more return-value detail would help.

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 only 33%, but the description compensates for key parameters: target is explained as optional comparison for drift, groupBy sector is tied to NSE classification by ISIN/symbol, and positions are described as the list to compute over. It leaves some exact format details to the schema.

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?

States specific verb 'Compute', resource 'allocation weights and concentration', and names concrete outputs HHI and effective holdings count. This clearly differentiates it from sibling tools like get_holdings or compute_xirr.

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 conveys clear context: use for allocation/concentration over a list of positions, with optional target drift comparison and standard sector grouping. It does not explicitly name exclusions or alternatives, so not a 5.

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