Get Company Profile

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

The description adds behavioral details beyond the readOnlyHint annotation: it explains the tool returns trading-halt status fields (halted/haltCode/haltedAt) and clarifies the behavior when trading normally (false/null). It also states this is a 1-credit operation, providing cost context.

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, efficient and front-loaded. Every sentence adds value: first sentence states purpose and outputs, second sentence provides usage guidance and behavioral note.

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 tool is a simple lookup with one parameter and an output schema exists, the description covers all essential aspects: what it does, when to use, what it includes, and a special behavioral note about trading halt status.

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 schema covers the single parameter ticker with a clear example. The description does not add deeper semantic meaning to the parameter but reinforces its purpose. With 100% schema coverage, baseline 3 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 it retrieves an enriched company profile using a ticker symbol and lists specific returned fields (CIK, exchange, sector, etc.). It also distinguishes from a 'full bundle' tool, helping the agent understand its 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?

The description advises using this for basic company info rather than the full bundle, and notes it is a lightweight lookup (1 credit). It does not explicitly name a sibling tool for the full bundle but provides clear guidance on when to use this tool.

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