get_profile

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but the description says nothing about session/auth requirements, whether the call is idempotent, or what the profile actually contains (user id, broker, enabled exchanges/products), all of which matter for a zero-parameter account call.

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?

A single front-loaded sentence that identifies the resource immediately, with no filler, hedging, or redundant restatement of the name. Nothing in it could be cut.

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 no-param, no-annotation, no-output-schema tool, the definition is minimally adequate: an agent knows what it fetches but not what fields come back or what auth state is needed. A brief note on the returned profile shape would close the gap that annotations and the output schema would otherwise fill.

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 tool takes zero parameters, so the baseline is 4 and there is no schema surface for the description to compensate for. The description does correctly signal that no user identifier is accepted by specifying the 'logged-in' user.

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 names a specific verb ('Get') and resource ('profile') and scopes it to the authenticated Kite user via 'logged-in'. No sibling tool returns account/profile data, so it is distinguishable in practice, though the description never explicitly contrasts itself with siblings like get_holdings or get_margins.

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 statement of when to call this tool versus alternatives, no prerequisites, and no note that it must be called after authentication. The 'logged-in' phrase only weakly implies that a valid session is required; everything else is left to inference.

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