get_ltp

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

With no annotations, the description must carry the behavioral load, and it does disclose a real prerequisite: a paid Kite Connect subscription with market data access, which rules out free-tier callers. It says nothing about whether prices are real-time vs delayed, rate limits, or what happens when an instrument is invalid.

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, no waste, with the capability front-loaded and the access restriction following immediately. Nothing needs trimming or reordering.

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 one-parameter read tool this is close to adequate, and the subscription caveat is a meaningful addition. However, with no output schema and no annotations, the description leaves the return shape (one price per instrument? ordered? keyed by symbol?) and freshness semantics unstated.

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 description coverage is 100% and the schema already documents the 'EXCHANGE:TRADINGSYMBOL' format and the 50-item max. The description's 'up to 50 instruments' merely restates maxItems, adding no format, batching, or error-handling detail beyond 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 a specific verb+resource ('Get last traded price') and the scope ('up to 50 instruments'), so an agent knows exactly what data comes back. It does not differentiate itself from siblings like get_quote or get_ohlc, which return related market 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?

Usage is only implied by naming the result (LTP). Nothing says when to prefer this over get_quote or get_ohlc, or that this is the lightweight option for bulk price checks versus full quote retrieval.

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