Get INDstocks profile

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

With no annotations, the description carries the full burden, and it does disclose key behavioral traits: it is a read-only fetch, requires an authenticated token, and is inexpensive to call. It does not describe error behavior or response format, but for a side-effect-free, zero-parameter endpoint this is sufficiently transparent.

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 exactly two sentences with no filler. The first sentence states the operation, and the second adds a concrete decision-useful purpose, making every word earn its place.

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 zero-parameter read endpoint, the description provides all essential context: what resource is fetched, that it requires an authenticated user, and why an agent would call it. No output schema exists, but the absence of inputs and side effects means nothing blocks correct invocation.

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?

This tool has zero parameters and the schema coverage is 100%, so there is no parameter-level meaning for the description to add. The baseline of 4 applies because no input guidance is needed.

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 ('Fetch') and names a concrete resource ('authenticated user's INDstocks profile'), making the tool's target unambiguous. The additional sentence about token validation further sharpens its purpose and differentiates it from sibling tools about holdings, orders, and schemes.

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 explicitly tells agents when to use this tool: as the cheapest way to confirm the API token is valid and not expired. It does not name alternatives such as refresh_token or diagnose_endpoints, nor does it list exclusions, but the primary use case is clear.

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