get_director_shareholding

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

No annotations provided. Description indicates read-only behavior ('Shows') but lacks details on rate limits, authentication, error handling, or data freshness. Sufficient for a simple query tool but not fully transparent.

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?

Two sentences, no redundancy. First sentence states purpose, second lists output fields. Front-loaded and efficient.

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 no output schema, the description adequately summarizes return fields. Tool is simple with one parameter, and description covers the essential output. Could mention error cases or data range but not critically 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?

Schema coverage is 100% with parameter 'stock_code' described as 'Securities code, e.g. 2330.' Description adds no further semantic detail beyond the schema. Baseline score of 3 is appropriate since schema already handles the parameter documentation.

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 the tool queries TDCC director/supervisor custody data with specific verb 'Query' and resource. It lists exact data items (custody shares, mandatory custody total shares, issued shares). Sibling tools address different data domains (voting, fund NAV, securities info, etc.), so this tool is well-distinguished.

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?

Description implies usage for querying director/supervisor shareholding by stock code but does not provide explicit when-to-use or when-not-to-use guidance. No exclusions or alternatives mentioned.

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