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

The readOnlyHint annotation already declares the operation is safe, so the description does not need to repeat that. It adds the REST method, which is a minor detail but does not disclose deeper behaviors like return format, pagination defaults, or rate limits. With annotations covering safety, this is an acceptable but not enriched transparency level.

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 extremely concise with two short sentences that state the purpose and the REST endpoint. Every sentence earns its place without redundant or verbose content, making it well-structured and easy to parse.

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?

Given the tool's simplicity (two optional pagination parameters, no output schema), the description combined with the readOnlyHint and complete schema provides sufficient context for an agent to invoke it correctly. While return details are not specified, it remains a basic list operation. This is more complete than a bare tautology but less rich than tools that need extra behavioral caveats.

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?

The input schema covers 100% of parameters with descriptions for page and per_page. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline 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?

The description clearly states 'List companies' with a specific verb and resource, and further specifies the Freshdesk REST endpoint 'GET /companies'. This distinguishes it from sibling list tools like freshdesk_list_agents or freshdesk_list_tickets by naming the resource directly.

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 guidance is provided on when to use this tool versus alternatives such as freshdesk_get_company for a single company or other list_* tools. The description only restates the tool's function without any contextual when-to-use or exclusion information.

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