ksef_add_source_document

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the agent knows it modifies state without destruction. The description adds that the document is indexed for advisory retrieval, providing additional context beyond annotations. However, it lacks details on idempotency, side effects, or behavior on duplicates.

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 a single, concise sentence with no filler. It is front-loaded with the core action and purpose, earning its place without redundancy.

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 5 parameters, no enumerated values, and an output schema, the description is too brief. It omits essential context such as whether the tool requires an active session, how it handles duplicates, or any constraints on content size. The output schema exists but the description does not hint at return values or error conditions.

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 0%, but the description adds no parameter-level information. Parameter names (title, content, content_type, origin, metadata) give some meaning, but the description does not clarify their roles, defaults, or constraints, leaving a significant gap for the agent.

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 stores a local source document and indexes it for advisory retrieval. It uses a specific verb ('Store') and resource ('local source document'), effectively distinguishing it from siblings like ksef_search_source_documents (search) and ksef_extract_invoice_source (extract).

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 or when not to use it. The description does not mention prerequisites, context, or exclusions, leaving the agent to infer usage based solely on the action described.

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