evidence_create

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

No annotations provided, so description carries full burden. Only states that it creates a record, but does not disclose any behavioral traits such as authentication requirements, side effects (e.g., duplicate checks), or what happens with nested data.

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?

Single sentence, no unnecessary words. Efficiently conveys the core purpose.

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 the generic nature of the tool (any evidence) and the presence of an output schema, the description lacks completeness. Does not explain valid evidence names are limited to specific system objects, nor that data structure must match the evidence's fields. Sibling tools for specific evidences suggest the agent may need additional guidance.

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 100% (both parameters have descriptions). The description does not add meaning beyond the schema, which already explains evidence name with examples and data as dictionary. Baseline 3 is appropriate.

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?

Description uses specific verb 'Create' and resource 'new record in any AbraFlexi evidence'. It clearly distinguishes from sibling tools that are specific to certain evidence types (e.g., contact_create, invoice_issued_create).

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 generic create vs specialized creates like contact_create. Does not state that this tool is for evidence types without dedicated tools, nor does it mention any prerequisites or limitations.

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