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

Beyond the safety hints in annotations, the description lists the specific data fields returned (date, description, amount, contact, project). This informs the agent exactly what kind of data structure to expect in the output.

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 definition is concise, presenting the function and scope in one dense sentence. The information is front-loaded with 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?

The definition is highly complete for a retrieval tool. It defines the scope, provides the dependency (schemes), and specifies the result structure, leaving no critical operational details missing.

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?

Since the input schema coverage is 100%, the description cannot add new semantic value to the parameters. It maintains the baseline score of 3, though the contextual reference to the prerequisite tool helps mitigate low semantics.

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 tool clearly states its purpose: listing transactions booked on a single general ledger account within a specific date range. It provides the output fields (date, description, amount, etc.), which aids clarity.

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?

The description provides a crucial workflow guideline by directing the user to the prerequisite tool (yuki_get_gl_account_scheme) for obtaining valid account codes. This guides the agent on the necessary sequence of calls.

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