get_register_records

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

No annotations are provided, so the description must cover behavior. It mentions filtering but does not disclose that it is a read-only operation, nor does it clarify pagination, sorting, or side effects. The 'get' verb implies non-destructive, but not explicit.

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?

Two short, front-loaded sentences. First sentence states the main action and filtering capability. No unnecessary words; every sentence 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?

Given 5 parameters, no output schema, and no annotations, the description is minimal. It does not explain output format, ordering, or default limit behavior. It suffices for basic understanding but lacks depth for complete autonomous use.

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 100% with adequate descriptions in the schema (full_name, filter JSON, period_from, period_to, limit). The description adds no further parameter context beyond stating filtering by dimensions and period, which is already covered.

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 gets register records with filtering by dimensions and period, and specifies the types of registers it works with (information, accumulation, accounting). This distinguishes it from siblings like get_register_dimensions and write_register_records.

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 this tool is for reading register records with filters, but does not explicitly state when to use it vs alternatives like get_register_totals or write_register_records. No when-not-to-use or context provided.

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