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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the returned field inventory and the underlying endpoint, but says nothing about pagination behavior or result-set size limits beyond what the schema already documents.

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?

Two short sentences with the resource and result fields front-loaded; no padding. The trailing 'GET /companies' is endpoint trivia that an agent doesn't strictly need, but it costs almost nothing.

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 12-parameter list tool with no output schema, the description helpfully enumerates returned fields, but it omits defaults (page 1, per_page 25) and pagination semantics that matter for correct repeated calls. Adequate but leaves real 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 description coverage is 100%, so every filter (city, name, tag_ids, owner_id, date ranges) and pagination parameter is already fully documented in the schema. The description's mention of address, phones, tags and pipeline totals loosely maps to owner/tag filters and returned fields but adds no syntax or constraint detail.

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 pair ('List or search') and the resource ('companies'), plus the field set returned. An agent can tell this is the collection endpoint rather than a single-company fetch, though no sibling (e.g., pipelinecrm_get_company) is named explicitly.

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?

No when-to-use guidance and no alternatives named. It does not say to use pipelinecrm_get_company for a single record or pipelinecrm_list_company_people for associations, leaving routing to inference from the tool name alone.

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