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

Annotations supply only destructiveHint=true, so the description carries nearly the whole behavioral burden. It discloses nothing about duplicate-name handling, whether creation is idempotent, what the response contains (no output schema exists), or auth/scope requirements; the REST endpoint note is mildly useful but not behavioral.

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?

Three short fragments, front-loaded with the verb+resource and the required field; nothing is padded. It is efficient but so terse that structure is doing little work.

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 an 8-parameter create with a nested passthrough object and no output schema, the description omits the return shape (id/handle?), duplicate behavior, and any auth context. The fully documented schema covers the field-level gaps, keeping this at minimum-viable rather than deficient.

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%, so the baseline is 3. The description only restates that `name` is required and never explains the non-obvious semantics of the `extra` passthrough object or the flattened address/link fields, so it adds nothing 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 ("Create a new company") that maps cleanly onto the sibling set (get/list/update variants are obviously different operations). It stops short of 5 because it adds no differentiation beyond what the tool name already conveys, and does not say how it relates to twenty_create_person/opportunity or when a company should be created first.

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 (workspace, auth, whether the company must already exist for opportunity linking), and no alternative or exclusion mentioned. The only actionable steer is the required-field note, which is already schema information.

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