frappe_create_document

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

With no annotations, the description carries full burden. It discloses that credential/password fields are stripped automatically, which is a useful behavioral detail. However, it does not cover other behaviors like idempotence, side effects, or required permissions, leaving significant gaps.

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 concise sentences with no wasted words. Front-loaded with the core action, and the behavioral note is appended efficiently. Ideal length for a simple tool.

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 tool has two parameters (one with nested object with additionalProperties), no output schema, and no annotations, the description is insufficient. It does not explain how to construct the 'values' object, required vs optional fields, or what the response looks like, leaving the agent to guess or rely on naming conventions.

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%—neither 'doctype' nor 'values' have descriptions in the schema. The description adds no parameter-level guidance (e.g., format of doctype, structure of values object, required subfields), failing to compensate for the missing schema documentation.

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 'Create a document' clearly states the primary action (create) and resource (document), but it does not differentiate from sibling tools like frappe_update_document or frappe_submit_document, missing context on what kind of document or specific use case.

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 alternatives (e.g., frappe_update_document for existing documents, frappe_list_documents for reading). Lacks exclusions, prerequisites, or context for selection.

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