Prepare Dividend Distribution

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

With no annotations providing hints, the description fully discloses behavioral traits: draft entries, CIT books to P&L, retained earnings debited only net, and hard-blocks based on retention and net assets.

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?

Every sentence adds unique value; the description is dense without being verbose, efficiently conveying purpose, constraints, and key behavioral nuances.

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 core functionality and constraints well, but lacks explicit explanation of the return structure (e.g., draft journal entries format). Still sufficient for an agent with accounting domain knowledge.

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?

All 11 parameters have schema descriptions, and the tool description adds significant context (e.g., retained earnings account debited with net, income tax expense account as P&L line, restricted reserves non-distributable).

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 calculates dividend CIT and creates draft journal entries, distinct from sibling accounting tools by focusing on dividend distributions.

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?

Provides explicit context for when to use (dividend distributions) and constraints (hard-blocks unless force=true), but does not directly contrast with sibling tools like create_journal or suggest alternatives.

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