getSales

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

Annotations already mark it as read-only, non-destructive, idempotent, and open-world. Description supplements with concrete behavioral details: default time range, filter capabilities, and pagination behavior. No contradiction with annotations.

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?

Description is moderately concise, packing many details into three sentences. It front-loads the main purpose and uses references to schema and siblings. Slightly dense but clear.

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 complexity (22 params, no output schema), the description covers defaults, filters, pagination, and alternative tools. It lacks explicit mention of return format but compensates with field selection and sibling references.

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?

Input schema covers all 22 parameters with descriptions (100% coverage). Description adds a high-level grouping of parameters but relies on schema for specifics. Baseline 3 is appropriate given full schema coverage.

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 it retrieves a list of sales orders (受注データを一覧取得します). It distinguishes itself from siblings by listing alternatives: getSale for specific order, statSale for aggregation, updateSale/cancelSale/sendSalesMail for write operations.

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 usage guidance: default to last 1 week, date range by order or update date, filtering by buyer, payment/delivery/cancel status, email states, pagination with limit/offset, field selection. Directly references sibling tools for alternative operations, helping agents choose correctly.

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