get_sse_company

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

No annotations are provided, so the description carries the full behavioral burden and does not meet it. It says nothing about what happens with an unknown or malformed ticker, whether the lookup is cached, auth requirements, or rate limits, which matters for a resolution tool with zero annotation coverage.

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?

One short, front-loaded sentence with no filler, and the identifying constraint (6-digit SSE ticker) appears before the parenthetical source. It is efficient, though the extreme brevity leaves structure with little room to add routing or caveats.

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 tool is simple (one fully-documented parameter, output schema present so return values need no explanation), so most information needs are already covered by structured fields. What is missing is usage routing against the many sibling company/section/filing tools and any behavioral notes, but the gap is modest given the low complexity.

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 description coverage is 100% and the single parameter already documents the accepted ticker prefixes (600xxx/601xxx/etc.), so the schema does the heavy lifting. The description only repeats '6-digit ticker' and adds the sse.com.cn source, which is a marginal gain over the baseline.

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?

States a specific verb ('Resolve') and resource ('SSE-listed company') and pins the identifier to a 6-digit ticker, which cleanly separates it from siblings like get_szse_company, get_bse_company, and get_hk_company. The only softness is that 'resolve' doesn't say exactly what is returned, though the exchange qualifier carries the disambiguation.

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?

There is no when-to-use guidance, no mention of alternatives (e.g., get_company for a generic lookup, get_sse_section/get_sse_interaction for other SSE data), and no stated preconditions. Usage can only be inferred from the verb-resource pair.

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