kite-mcp

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the 'placed today' filter which defines the query window, but omits behavioral details like pagination limits, timezone handling for 'today', or whether rejected/cancelled orders are included.

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?

Five words forming a single sentence: 'Get all orders placed today.' Front-loaded with the action verb, no repetition of structured data, zero waste.

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?

Sufficient for a simple read operation with output schema provided, but lacks financial-domain specifics such as trading session vs calendar day definitions, timezone (trading venue time vs UTC), or empty-state behavior when no orders exist.

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?

With zero parameters (schema coverage 100% of empty set), baseline 4 applies. The phrase 'Get all' appropriately signals that no filtering parameters are required, aligning with the empty input 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?

The description 'Get all orders placed today' provides a specific verb (Get), resource (orders), and scope (placed today). However, it does not explicitly differentiate from sibling mutation tools like cancel_order or modify_order, which also operate on orders.

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?

While the 'today' constraint implies temporal scope, the description offers no explicit guidance on when to use this versus alternatives (e.g., get_historical_data), prerequisites like authentication via kite_login, or lifecycle state (open/executed/cancelled).

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