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

The annotations declare destructiveHint=true, so the write/mutation nature is already known. The description adds only the REST endpoint (POST /contacts) and no information about what gets created, whether duplicates are rejected, permissions needed, or failure behavior. It does not contradict the annotations, but it contributes little behavioral context.

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?

Very terse and front-loaded, but three clipped fragments read as under-specification rather than efficiency for a 12-parameter tool. The 'Freshdesk REST: POST /contacts' fragment offers little value to an agent already invoking the tool.

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 mutation tool with a nested custom_fields object and no output schema, the description is thin. It omits any mention of the nested object, duplicate/validation behavior, and the shape of the returned contact, leaving meaningful gaps for a create operation.

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 12 parameters (including the nested custom_fields object) are already documented in the schema. The description adds nothing beyond restating that `name` is required, so the 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?

States a specific verb and resource ('Create a contact'), which is clear and actionable. It does not distinguish itself from write siblings such as freshdesk_create_company or freshdesk_create_ticket, but the resource noun makes the target unambiguous.

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?

Only states that `name` is required. There is no guidance on when to use this versus freshdesk_update_contact, freshdesk_search_contacts, or freshdesk_create_company, and no prerequisites (e.g. duplicate handling, required auth scope) are mentioned.

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