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

Annotations supply only destructiveHint=true, leaving the description to explain mutation behavior. Beyond restating that name is required and citing the REST route 'POST /companies', it says nothing about side effects, whether the company is returned, or duplicate-domain handling. For a write tool with thin annotations, this is a real gap.

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 sentences, front-loaded with purpose and the required field. The REST endpoint reference is arguably redundant, but nothing is bloated or buried.

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?

With no output schema, the description should say what a successful call returns and cover error conditions. It omits both, and gives no context on the destructiveHint=true annotation, leaving an agent under-informed for a mutation tool with a nested custom_fields object.

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 all five parameters (including the nested custom_fields) are already documented in the schema. The description's only parameter note ('name is required') repeats what the schema's required array and field description already state, so baseline 3 applies.

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 states a specific verb and resource ('Create a company'), which cleanly separates it from siblings like freshdesk_get_company and freshdesk_list_companies. It does not explicitly name an alternative, so it falls short of a 5.

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 guidance on when to use this versus freshdesk_update_contact-style alternatives or how it relates to freshdesk_create_contact. No prerequisites, no mention of required permissions, no indication of what happens on duplicate names/domains.

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