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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description only needs to add behavioral context beyond that. It adds 'digital-presence detection' and 'full source provenance', which are meaningful behavioral traits not present in the annotations or schema. No contradiction with annotations.

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 two tightly packed sentences: the first states exactly what is returned and for which entity, and the second gives workflow position. There is no filler, no repetition of schema structure, and every sentence earns its place.

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 one parameter, an output schema, and annotations covering idempotency and non-destructiveness, the description provides the operational guidance needed to call the tool correctly. It tells the agent what to retrieve, how to obtain the required companyId, and when in the workflow to invoke it.

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 input schema has 0% description coverage, so the description must compensate. It explains that companyId is resolved by search_oman_company, giving useful provenance for the parameter. It does not detail the ID format, but with a single self-explanatory identifier and schema constraints (minLength/maxLength), this is sufficient.

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 names a specific verb and resource: 'Return a structured profile for one Oman company by companyId', and enumerates concrete content areas (identity, registration, location, contact, digital presence, provenance). It also distinguishes itself from siblings by positioning search_oman_company as the ID-resolution step and analysis/due-diligence tools as later stages.

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 description explicitly states the tool should be used after search_oman_company resolves a companyId, and before deciding whether deeper analysis or due diligence is warranted. This gives clear workflow placement and tells the agent where this tool fits among its siblings.

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