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

With no annotations provided, the description carries the full burden. It adds some value by detailing the data categories (salaries, stock awards, total compensation) and mentions 'filing details and links to official documents,' but it does not disclose behavioral traits such as pagination, rate limits, output format, or what happens for invalid symbols. It is somewhat transparent but lacks depth.

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 two sentences and front-loaded with the primary purpose. The second sentence elaborates with useful specifics. There is no redundant fluff and every clause adds information, making it appropriately concise for the tool.

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 tool with a single parameter and no output schema, the description provides a reasonable overview of expected data content, including filing details and links. However, it does not clarify the structure of the response (e.g., whether it returns an array of executives, multiple years of data) or any limitations. Given the low complexity, the description is nearly complete but leaves a minor gap in return format.

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% for the single parameter 'symbol,' which is described as 'Stock symbol.' The description does not add any extra syntax, format, or example for the parameter. Since the schema fully covers the parameter, the baseline score of 3 is appropriate; the description adds no additional semantic value beyond restating the resource type.

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 the specific verb 'Retrieve' and clearly identifies the resource as 'comprehensive compensation data for company executives.' It distinguishes itself from sibling tools like getCompanyExecutives (which lists executives) and getExecutiveCompensationBenchmark (which provides benchmark comparisons) by focusing specifically on compensation details, filing info, and document links.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of exclusions, prerequisites, or other tools that might be more suitable for different scenarios. The description only states what the tool does, not when to use it.

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