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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds the endpoint path and the returned field set, but says nothing about behavior on a name miss (empty result vs. error) or any permission requirements.

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 zero filler; the key constraint (exact name) and the payload contents are stated before the endpoint reference.

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 required parameter, no output schema, and no nesting, the description covers what is needed: the lookup key semantics and the returned fields stand in for a missing output schema. Only the not-found behavior is absent, which is a minor gap.

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 description coverage is 100% and the single parameter already carries 'Exact company name.', so the schema does the heavy lifting. The description's 'by exact name' merely reinforces the exact-match constraint rather than adding new syntax or format detail; baseline 3 applies.

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+resource ('One company by exact name') and enumerates the fields returned (description, phone, address, SLA, domains, departments, custom fields). It implicitly distinguishes itself from desk365_list_companies via 'one' vs. 'list', but never names the sibling, so differentiation requires mild inference.

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 phrase 'by exact name' tells the agent this is a lookup requiring an exact identifier rather than a search, which is useful selection signal, but there is no explicit when-to-use/when-not guidance or reference to list/search alternatives.

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