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

No annotations are provided, so the description carries the full behavioral burden. 'Read' implies a safe read operation, but the description says nothing about auth requirements, rate limits, persistence, or what 'structured agent profile' actually contains, leaving the agent to guess at behavior for a data-retrieval call.

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?

A single front-loaded sentence with no filler; the verb and the scope arrive immediately. It is efficient, but its brevity borders on under-specification rather than pure economy.

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?

With no output schema, no annotations, and an undescribed parameter, the description should compensate more than it does. It omits what the returned profile contains, what happens for an unknown slug, and whether authentication is required, so an agent lacks enough to call it confidently in edge cases.

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?

One required string param ('slug') at 0% schema description coverage, so the schema provides no meaning on its own. The description does clarify that the slug identifies a single company ('one company slug'), which is a real contribution, but it never specifies slug format (e.g., 'acme' vs 'acme.com'), so the gap is only partly closed.

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?

States a specific verb ('Read') and resource ('structured agent profile for one company slug'), scoped to a single company. It is distinguishable from search_companies and search_company_directory by the singular slug scope, though it never names those siblings to make the contrast explicit.

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?

There is no when-to-use guidance, no statement of prerequisites, and no mention of alternatives. The phrase 'one company slug' weakly implies this is the single-record counterpart to the search siblings, but the agent must infer that entirely.

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