search_company_context

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

No annotations provided, so description carries full burden. It discloses that the endpoint is paid and returns x402 challenges in default non-settling mode, which is valuable behavioral context. However, it does not confirm read-only status, idempotency, or success behavior.

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 sentence, front-loaded with key function. Adequately concise, though could be more structured with separate usage notes.

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 one param, no output schema, and no annotations, the description covers key behavioral aspects (paid, x402) but lacks information on return format or what constitutes 'company context.' Incomplete for full autonomous use.

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 parameter 'q' is described as 'Company search query.' The description adds the endpoint path but no additional semantic meaning beyond the schema, resulting in minimal value added.

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 explicitly states it is a thin wrapper for a search endpoint, clarifying its role as a company search tool. However, it does not differentiate from siblings like get_company_risk_summary beyond being a search.

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?

Mentions paid endpoint and x402 challenge in non-settling mode, but provides no context on when to use this tool over alternatives or when not to use it. No explicit when-to-use or when-not-to-use guidance.

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