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

Annotations already mark this as read-only and non-destructive. The description adds a valuable behavioral/operational constraint: the login session dependency and account_link_id matching requirement. This goes beyond the annotations by telling the agent what must be true before calling the tool.

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?

Three tightly written sentences with no filler. The required login prerequisite is front-loaded, followed by the core purpose and parameter usage. Every sentence earns its place.

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?

For a simple read-only summary tool with 100% schema coverage and only one required parameter, the description is sufficient. It covers the critical login prerequisite and parameter usage; because there is no output schema, a bit more detail about the expected result (e.g., total amount fields) could have been added, but this is minor.

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 100%, so the schema already documents all parameters and their types. The description adds helpful usage semantics by pointing to cmtt_yr as the target year and qrt as the optional quarterly filter for 1-4, reinforcing how the parameters work together.

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 clearly states a specific verb and resource: 'Search cash receipt sales annual summary.' The use of 'annual summary' and optional 'quarterly breakdown' differentiates it from sibling tools like hometax__cash_receipt__sales__search_history, which would handle detailed transaction search.

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?

Explicitly states the required prerequisite: a prior hometax__session__login call with the same account_link_id. It also tells the agent to use cmtt_yr for the target year and qrt for quarterly breakdown, giving clear context for invocation, though it does not explicitly describe when to prefer this tool over related history-search siblings.

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