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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds two useful facts not in annotations: only public profiles are readable, and results carry official domain and description provenance; it does not cover behavior for unknown or private IDs.

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?

One front-loaded sentence with the resource and lookup key stated first, and no filler. It is efficient, though very terse given the absence of usage guidance.

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 single-parameter read tool with full schema coverage, annotations covering safety, and no output schema, the description is nearly sufficient. It signals public-only scope and the nature of returned data; only error/not-found behavior is left unstated.

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 single parameter has 100% schema coverage, including length bounds, opacity, and URL-encoding guidance, so the schema does the heavy lifting. The description only restates that lookup is by ID, adding no semantics beyond the schema.

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 and resource: 'Read a public employer profile by ID.' The word 'public' plus 'employer profile' separates it from get_company_jobs and search_companies, though no sibling is named explicitly, so sibling differentiation is only implicit.

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 'by ID' phrasing and the schema's note that the ID is 'returned by search' imply you must call search_companies first, which is useful implied usage. But there is no explicit when-to-use/when-not statement or named alternative for cases where you only have a name.

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