dosare_create

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

Discloses that title and C168 deadline are derived automatically from subject fields. No mention of side effects, permissions, idempotency, or return value. With no annotations, this is a partial disclosure.

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?

Organized into a clear opening statement, a specific rental-contract instruction, an alternative-tool directive, and a list for other types. Slightly dense but not overly verbose.

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?

Covers the main use cases and the majority of parameters (type, subject, title, deadlineAt, deadlineLabel, nextStep, notes). Missing details about 'status' and 'companyId' fields, and does not describe output or error behavior, but sufficient for typical creation.

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?

Adds substantial meaning to the subject object by listing and explaining each field (numar, data, adresa, etc.), and clarifies that title/deadlineAt are derived. The schema itself has low coverage, so this description fills critical gaps.

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?

Clearly states the tool creates a dosar and differentiates between rental contracts and other types. Names the alternative tool for yearly declarations, so an agent can select correctly.

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?

Explicitly directs to use dosare_annual_return for yearly Declarația unică, and gives specific fields for rental contracts. However, it does not mention other dosar creation variants (e.g., C168, D212) that appear among siblings.

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