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

With no annotations, the burden falls entirely on the description. It only lists return fields but does not disclose behavioral traits like rate limits, idempotency, or any side effects. The read-only nature is implied but not stated, leaving gaps for an AI agent.

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 a single, clear sentence with no extraneous information. It efficiently conveys the tool's purpose and key outputs, making it easy to parse.

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 simple tool with one parameter and no output schema, the description adequately lists the data fields returned. However, it could be slightly more complete by specifying any limitations (e.g., US stocks only) or mention that it returns a single record.

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% and the parameter 'ticker' is documented. The description adds value by specifying the exact fields returned (sector, industry, employees, description, market cap), which goes beyond the schema and helps the agent understand what the tool provides.

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?

Description clearly identifies the tool as retrieving a company profile with specific attributes (sector, industry, employees, description, market cap). It distinguishes itself from sibling tools like 'get_all_financial_data' or 'compare_companies' by focusing on a summary profile, but could be more explicit about being for a single company.

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 siblings such as 'compare_companies' or 'get_all_financial_data'. The description does not indicate context, prerequisites, or alternative scenarios.

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