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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world scope, and the description's 'read-only' plus 'TZ-018 bridge' mostly restates that while adding a hint about the backing system. It does not say what happens when the ID is unknown (error vs. empty result) or anything about the response payload, which are the remaining behavioral unknowns.

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: verb and resource first, then the operational qualifiers in parentheses. Nothing could be removed without losing information.

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?

For a one-parameter read tool whose annotations already cover the safety profile, the description is close to sufficient, but it leaves the required identifier undocumented and gives no sense of what is returned (no output schema exists to cover that). It is adequate but with clear gaps.

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% — company_id is an undescribed plain string — and the description only implies that the value identifies exactly one company. It adds no format, source, or validation meaning (numeric vs. UUID, behavior on unknown ID), so it only partially compensates for the schema gap.

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?

Names a specific verb and resource ('Read one company's profile') with explicit single-record scope, which distinguishes it from list siblings like erp_list_organizations and from write siblings like erp_create_organization. It stops short of naming a sibling or stating what a 'profile' contains.

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 or when-not-to-use guidance. Critically, the description never says how to obtain a valid company_id (e.g., via erp_list_organizations), despite that being the sole required parameter, so an agent has no routing instruction for the prerequisite lookup step.

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