icici_status

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It states that the tool checks configuration status and provides token instructions, implying a read-only operation. However, it does not explicitly mention side effects, authentication requirements, or error behavior, leaving some 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, front-loaded sentence that conveys the tool's purpose without filler words. It is concise and easy to parse, with every word contributing meaning.

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 that the tool takes no parameters and an output schema exists, the description is sufficient for an agent to understand what the tool does and when to invoke it. It clearly names the broker API (ICICI Breeze) and the two key outputs (configuration status and token instructions).

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 has zero parameters, so the baseline is 4. The description adds context by specifying what the status check covers (configuration status and session token instructions), which helps the agent understand the tool's scope even though there are no parameter semantics to explain.

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 specific verb 'check' and clearly identifies the resource as 'ICICI Breeze API configuration status' with the added context of 'daily session token instructions.' This precisely distinguishes it from sibling tools like icici_live_quote or fyers_status.

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 clear context for when to use this tool: when checking ICICI Breeze API configuration status or retrieving daily session token instructions. However, it does not explicitly mention alternative tools or exclusions, so it stops short of being fully explicit.

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