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

The annotations only declare destructiveHint=true; the description adds nothing about write semantics beyond the word 'Create' - no permission requirements, no duplicate detection, no confirmation of what is persisted or returned. It does not contradict the annotation (creation is a mutation), but it carries almost none of the behavioral burden a mutating tool needs.

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?

Two short sentences, front-loaded with the essential action; the trailing 'Insightly: POST /Organisations' adds a small amount of endpoint context without bloat. No wasted filler, but also very little substance per sentence.

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 no output schema and only a destructiveHint annotation, the description omits required-field emphasis, return behavior, and error/duplicate handling. It is not sufficient for an agent to invoke this confidently beyond the bare minimum.

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 description mentions no parameters at all, while schema description coverage is only 42% across 12 parameters. Fields such as custom_fields, owner_user_id and the address block are undocumented in the description, so it fails to compensate for the schema's gaps.

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 an organisation (company)') plus the underlying API endpoint, so the action is unambiguous. It does not, however, distinguish itself from the sibling insightly_update_organisation or explain how a created organisation relates to create_contact/create_lead workflows.

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 create versus update an organisation, no prerequisites (e.g. required fields, duplicate-name handling), and no mention of alternatives among the many sibling creation tools. The agent must infer all of this.

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