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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed (non-open-world) data source, so the safety profile is covered structurally. The description adds one piece of context beyond them — the data is 'verified' — but says nothing about freshness, caching, or what happens when a requested field is absent.

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 resource come first. It is efficient, though it spends no words on the one place guidance would help most (when to call it).

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 zero-required-parameter read tool with full schema coverage and annotations that already carry the safety profile, this is close to sufficient; the output has no schema, but the description at least characterizes the returned content (company, contact, handoff). 'Handoff information' remains vague but is not blocking.

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 100% and the single 'fields' parameter is fully documented in-schema, including its enum and the omit-for-all behavior. The description adds no meaning beyond that, so the baseline of 3 is appropriate.

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 ('Get') and a specific resource set ('company, contact and handoff information') scoped to a named company, which is clearly distinct from the material- and handoff-mutation siblings. It stops short of explicitly differentiating itself from start_project_handoff, but the resource named is unambiguous.

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 prerequisites, and no mention of alternatives among the sibling tools. The agent must infer that this is the reference-data call to make before project handoff work, with nothing in the text supporting that inference.

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