etf_profile

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Fetch' implies a read operation, but it doesn't specify if it's idempotent, has rate limits, requires authentication, or what the output format might be. For a data-fetching tool with zero annotation coverage, this is a significant gap in transparency.

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 extremely concise with just two words, 'Fetch ETF profile', which is front-loaded and wastes no space. While it may be under-specified, it earns a high score for brevity and clarity within its limited scope.

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 the complexity of financial data tools, no annotations, no output schema, and low parameter coverage, the description is incomplete. It doesn't cover behavioral aspects, output details, or usage context, making it inadequate for an agent to effectively use this tool without additional assumptions or errors.

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 input schema has 1 parameter with 0% description coverage, and the description provides no additional parameter information. It doesn't explain what 'symbol' represents (e.g., ticker format, examples, constraints), leaving the agent to guess. With low schema coverage, the description fails to compensate, resulting in inadequate parameter semantics.

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 'Fetch ETF profile' states a clear verb ('fetch') and resource ('ETF profile'), which is better than a tautology. However, it lacks specificity about what an 'ETF profile' contains and doesn't differentiate from siblings like 'company_overview' or 'stock_quote', which might provide similar financial data. The purpose is understandable but vague in scope.

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. The description doesn't mention prerequisites, context, or exclusions, such as whether it's for real-time data, historical info, or how it differs from other financial data tools in the sibling list. This leaves the agent without direction on tool selection.

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