unit_trust_comparison

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

With no annotations, the description carries the full burden of behavioral disclosure. 'DEMO' signals a demo mode, but it does not explain data freshness, limitations, or how typical returns are derived, leaving significant ambiguity.

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 concise sentence plus the 'DEMO' label, front-loaded with the core purpose and free of unnecessary words. It is highly scannable and efficient.

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?

An output schema exists, reducing the need to explain return values. However, the description omits how risk_profile influences the comparison and what 'typical returns' means, making it adequate for a simple demo tool but incomplete for deeper understanding.

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 only parameter, risk_profile, is not mentioned in the description, and the schema has no description either. With 0% schema coverage, the description adds no meaning to the input parameter.

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 clear verb 'Compare' and specifies the resource 'Kenya unit trust fund types and typical returns.' This distinguishes it from sibling tools like nse_equities_guide and treasury_bond_calculator, which cover different investment products.

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?

There is no guidance on when to use this tool versus alternatives, nor any scenario-based recommendations. The 'DEMO' label hints at non-production use but does not explicitly state when to invoke or avoid the tool.

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