search_companies

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

No annotations provided, but the description implies a read-only operation with no side effects. Discloses return type (symbols and URLs) but lacks details on rate limits or data freshness. Adequate for a search tool.

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?

Single paragraph with docstring format, front-loaded with purpose, followed by parameter details. No unnecessary words, efficient and clear.

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?

Indicates return values (symbols and URLs) and provides limit parameter for control. Output schema exists (not visible but noted). For a search tool, this is sufficient; missing details like pagination are minor.

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 0%, yet description adds significant context: example values for 'query' and valid range for 'limit'. This fully compensates for the lack of schema descriptions, making parameters self-explanatory.

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?

Clearly states it searches Indian stock market companies by name and returns symbols and URLs. The verb 'search' and resource are explicit, and it distinguishes from siblings like 'get_company' which likely returns details for a specific 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?

Provides example queries and limit parameter, giving clear context for use. Does not explicitly state when not to use or mention alternatives, but the purpose is intuitive enough for an agent to infer appropriate usage.

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