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

With no annotations, the description carries the full behavioral burden. It usefully discloses the default ordering when code is omitted (AI-theme stocks prioritized) and the upstream source, but omits any rate limits, auth needs, or data freshness beyond the source table name.

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?

A single front-loaded sentence with the domain tag leading and no wasted words. The bracketed tag is slightly cryptic but 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?

For a 2-param news-listing tool with no output schema and no annotations, the description names the return content (headlines), the source, and the filter default. It is adequately complete, missing only return-shape or freshness details.

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%, so both parameters (code, limit) are already documented. The description adds that code acts as a filter with a default-priority fallback, marginally enriching it, but offers no format/syntax detail beyond the schema.

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 (get) and resource (TW-listed companies' daily material news headlines), names the data source (TWSE t187ap04_L), and tags the domain (themes/high-dividend). It is clearly distinguishable from quote tools, though it does not explicitly contrast with get_theme_stocks.

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 explains the optional-filter behavior of code ('可依代號篩選；不填則...'), which is implied usage guidance. However, it gives no explicit when-to-use vs alternatives (e.g., get_theme_stocks) and no prerequisites.

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