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

With no annotations, the description carries the burden of behavioral disclosure. It implies a read-only profile lookup and mentions 'Pro,' but it does not explain access requirements, data freshness, or any constraints. This is adequate for a simple get tool but not richly transparent.

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 short and packs the key content into a compact structure. The 'INFLUENCE' prefix and 'Pro' tag are somewhat cryptic, but the core meaning is front-loaded and there is no redundancy.

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?

The description lists the major return contents and makes the singular-company scope clear. However, with no output schema and no parameter format details, an agent may still need external context to know what slug format to use and how the response is structured.

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 documents the optional context parameter well, but the required slug parameter has no description. The tool description adds the meaning that the slug identifies one company, which helps, but it does not specify expected format or where the slug comes from.

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 the tool returns a full demand-side profile for a single company, including 40-dimension readiness scores, adopted stack, and per-quarter history. It is specific about the resource and contents, though it does not explicitly differentiate itself from siblings such as find_company_insights.

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 usage is implied: when an agent needs a detailed profile for one specific company rather than a search across companies. However, it gives no explicit guidance about when to prefer this over related tools like find_company_insights or how the 'Pro' label affects eligibility.

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