Get a CRM company

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

The description adds behavioral context beyond annotations by stating 'Throws if the company id isn't found,' which is not indicated in readOnlyHint/openWorldHint. It correctly reflects readOnlyHint=true and discloses an error case.

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?

The description is two short sentences, front-loading the primary action and adding a single behavioral note. No extraneous content.

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 simple getter with no output schema, the description adequately conveys the return scope ('full company record including its contacts') and error behavior. Annotations cover read-only and world model limits.

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?

With 50% schema description coverage, the description does not enhance parameter information. It mentions 'contacts' but not how they relate to parameters. The 'id' parameter has a schema description, but 'project' is undocumented and the description offers no additional guidance.

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?

The description clearly states 'Full company record including its contacts' and specifies error behavior. The name 'get_company' aligns with sibling 'list_companies' and 'add_company', distinguishing it as a single-record retrieval.

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?

While the description implies use for fetching a specific company with contacts, it does not explicitly state when to use this tool versus alternatives like 'list_companies' nor provides when-not or prerequisites.

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