sbis_list_documents_by_event

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

No annotations exist. The description gives no information about side effects (e.g., read-only nature), authentication needs, rate limits, or pagination behavior. Minimal transparency; the tool is likely read-only but not stated.

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 short (a single line), which is concise but at the expense of completeness. It front-loads the three registry types, but lacks structure or elaboration.

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 8 parameters and no output schema, the description is severely incomplete. It does not explain pagination, filtering, state, or counterparty INN. The agent has insufficient information to use the tool correctly.

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 description coverage is 0%, so the description must compensate. It only adds context for registryType by listing its enum values. Other parameters (page, limit, dates, etc.) are left entirely unexplained, leaving the agent with no semantic guidance.

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 mentions 'Registry lists' with three categories (incoming/outgoing/responses), which implies listing documents by event type. However, it does not explicitly state 'list documents by event' in English, and the verb is implicit. The purpose is somewhat clear but vague.

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?

No guidance on when to use this tool versus siblings like sbis_list_documents. No context on prerequisites or exclusions. The description provides no usage direction.

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