get_unsorted

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

No annotations are provided, so the description must disclose behavioral traits. It only states the purpose, not behavior like pagination, sorting, or the effect of parameters. The agent learns nothing about rate limits, authorization needs, or whether this operation is safe (read-only).

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 sentence with no unnecessary words. It is front-loaded and efficient, conveying the core purpose without verbosity. Every word earns 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?

With no output schema and no annotations, a brief description is insufficient. The tool has three parameters, but the description does not explain how they filter or what the response contains. Essential context like return format, unsorted pipeline distinctions, and default behavior is missing.

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?

Schema coverage is only 33% (only pipeline_id has a description). The description does not compensate by explaining the parameters. For example, 'category' and 'limit' have no semantic guidance beyond the schema's enum values and type. The description adds no value over what the schema already provides.

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 unsorted leads (incoming leads not yet in funnel). This distinguishes it from sibling tools like get_leads, which likely retrieve leads already in the funnel. The one-sentence Russian description is specific enough to convey the resource and action.

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 guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites mentioned. The description only implies usage for unsorted leads without contrasting with other lead-related tools. This lack of context leaves the agent without clear decision criteria.

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