kalshi_structured_targets

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

With no annotations, the description provides some behavioral details: pagination via cursor and page_size, and the return format. However, it omits rate limits, auth requirements, or side effects. Adequate but not comprehensive.

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 very concise—two sentences—with no wasted words. It front-loads the core purpose and follows with pagination and output details.

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 the tool has 3 parameters and no output schema, the description adequately covers the purpose, pagination, and return structure. However, it lacks explanation of the 'type' parameter and full details of the structured_targets items beyond field names.

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 0% schema coverage, the description partially explains cursor and page_size ('Paginated by cursor; page size via page_size') but does not explain the 'type' parameter. This adds meaning for two of three parameters but is incomplete.

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 clearly states the tool retrieves Kalshi's entity registry (players, companies, people) that markets resolve against. It specifies pagination and return structure, distinguishing it from similar single-entity tools like kalshi_structured_target.

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 implies usage for fetching entity lists but does not explicitly state when to use this tool versus alternatives (e.g., kalshi_structured_target for a single target). No when-not-to-use conditions are mentioned.

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