Check your Sieve API usage for the current billing period.
Shows screens used, monthly limit, tier, and organization name.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, providing the safety profile. The description adds the specific return fields (screens used, monthly limit, tier, organization name), which is useful but does not introduce deeper behavioral traits like pagination or rate limits. No contradictions exist.
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 two sentences: the first states the purpose, the second lists what it shows. It is front-loaded and entirely waste-free, with no redundant phrasing.
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-only usage tool with an output schema present, the description sufficiently covers the tool's purpose and return content. There are no missing prerequisites or complex behaviors that would require further explanation.
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 has zero parameters, so the description carries no parameter burden. It does not need to explain inputs, and the baseline of 4 applies. No additional parameter semantics are necessary.
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 specifies the verb 'Check' and the resource 'Sieve API usage for the current billing period', which distinguishes it from sibling tools like sieve_status (service status) and sieve_screen (screen-related). It is concise and unambiguous.
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 context: when you need to check API usage for the current billing period. It does not explicitly exclude alternatives or mention when not to use it, but the scope is clear enough for the agent to select it appropriately.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct role in the screening workflow: dataroom listing vs adding, deal listing, screening, status polling, results retrieval, memo generation, and usage checking. No two tools have overlapping purposes.
All tools share the 'sieve_' prefix, but the pattern is inconsistent: some are pure nouns (sieve_deals, sieve_results), one combines resource and action (sieve_dataroom_add), and one is a verb (sieve_screen). Still, the names are readable and predictable once the domain is understood.
With 8 tools, the set is well-scoped and covers the entire lifecycle of a startup screening operation without unnecessary bloat. Each tool earns its place.
The core workflow is complete: add documents, screen, check status, retrieve results, generate memo, and list deals. Minor gaps exist, such as no update/delete for data room documents or a dedicated deal detail view, but agents can work around these.
