Get company

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

Annotations already declare readOnlyHint: true, so the description's 'retrieve' is consistent but adds no behavioral context beyond what annotations provide. No mention of authentication, rate limits, or side effects, but the read-only nature is already clear.

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 a single sentence that is front-loaded with the verb and resource. No wasted words; every part is essential for the core purpose.

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 read-only tool with 2 params and no output schema, the description is largely sufficient. However, it could mention that it returns the full company object or that results are scoped to the account, but overall it covers the essential context for a retrieve-by-id tool.

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 input schema already documents both parameters (account_id, company_id). The description adds no extra meaning beyond what the schema provides, meeting the baseline for param semantics.

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 'Retrieve a single company by id,' using a specific verb ('retrieve') and resource ('company by id'). This distinguishes it from sibling tools like list_companies (multiple retrieval) and delete_company (delete action).

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 description implies usage (when you need a single company by ID) but provides no explicit guidance on when to use vs. alternatives like list_companies or prerequisites. No exclusion criteria or context for when not to use this tool.

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