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

With no annotations, the description carries the behavioral burden and discloses important context: the tool uses the caller's OpenAny gateway credentials, and charges/authorization are determined by the gateway. It implies a read-only retrieval operation through the verb 'retrieve' but does not cover error behavior or rate limits.

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 front-loaded with the purpose and supported by a compact list of returned details and operational notes. It is appropriately sized, though the two-sentence close on credentials and charges could be slightly tighter.

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 three-parameter retrieval tool with no output schema, the description provides a useful summary of return content and points callers to a sibling API for discovering valid years. It leaves some ambiguity about identifier requirements when neither id nor tyshxydm is supplied.

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 baseline would be 3, but the description adds meaningful semantics by explaining that the enterprise can be identified by enterprise ID or unified social credit code and that year corresponds to the annual report reporting year. It still does not clarify whether exactly one identifier is required.

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 uses a specific verb and resource: retrieve structured details of an enterprise annual report for a specified year. It clearly scopes the result to annual report data and distinguishes the tool from sibling enterprise tools by naming the basic information API for checking available years.

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 gives clear context for use: provide an enterprise identifier plus reporting year, and use the Enterprise Basic Information API to check which years are available. It does not enumerate when to avoid this tool or list other report-related alternatives, but the intended usage is clear.

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