list_available_tickersReturns ticker symbols for companies with published RentSeek executive-compensation data. No authentication is required, and the request costs 0 credits. The result contains availability only, not compensation values. It is not investment advice.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (readOnlyHint=true, openWorldHint=false), the description clarifies that the result contains only availability, not compensation values, and adds a disclaimer that it is not investment advice. This provides useful context without contradicting annotations.
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?
Three sentences: purpose, cost/auth context, and scope disclaimer. All earn their place, no redundant text. Front-loaded with the core function.
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 and 0 parameters, the description adequately explains the returned data (tickers) and its limitation (no compensation values). It could mention ordering or if the list is exhaustive, but the current version is mostly complete for a simple listing tool.
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?
The tool has zero parameters and schema description coverage is 100% (trivially). The description does not need to add parameter meaning; its mention of 'no authentication' is behavioral, not parameter-related. Baseline 4 for 0 parameters is appropriate.
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 clearly states the tool returns ticker symbols for companies with published RentSeek executive-compensation data. It uses a specific verb ('Returns') and a well-defined resource, distinguishing it from sibling tools like get_company_dossier or get_executive_compensation.
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 notes that no authentication is required and costs 0 credits, implying low friction for use, but does not explicitly specify when to use this tool versus alternatives (e.g., for initial ticker discovery before fetching compensation). No exclusions or when-not-to-use guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of executive compensation data: claim evidence, full company dossier, compensation rows, ticker listing, and material changes. Descriptions clearly differentiate them, preventing confusion.
All tools follow a consistent verb_noun pattern using snake_case: get_* for retrieval and list_* for enumeration. No mixing of styles or irregular verbs.
Five tools is well-scoped for the domain of accessing executive compensation filing data. Each tool provides essential functionality without unnecessary bloat or gaps.
The tool set covers core operations: retrieving evidence, dossiers, compensation details, available tickers, and material changes. A minor gap is the lack of a direct tool for bulk compensation data across multiple companies, but the set is largely complete.