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

Annotations already declare a non-destructive, non-idempotent, closed-world write. The description adds useful context (it returns a signed URL, and only five document formats are accepted), but omits whether the URL expires, what auth/permissions are needed, and why calls are non-idempotent (each call mints a new URL).

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?

Single front-loaded sentence, no filler, and the scope qualifier ('organization-level') arrives before the trailing details. Every phrase earns its place.

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 mutation with no output schema, the description conveys the core action and format constraints but leaves the two-step upload workflow unspecified: it never says the returned signed URL must be used to PUT the file and then finalized via completeClarityOrganizationDocumentUpload, nor does it mention URL lifetime.

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 coverage is 67%, so the schema documents fileName and contentType. The description earns extra credit by mapping the raw MIME enum to human-readable formats, notably clarifying that BPMN corresponds to application/xml, which is not obvious from the enum alone. orgId remains undocumented anywhere but is self-describing.

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 (Create) and resource (signed URL for document upload) and scopes it as 'organization-level Clarity capture', which separates it from the team-level and unqualified document-upload siblings. It does not explicitly name or contrast those siblings, but the scope qualifier is enough to route an agent correctly.

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 on when to choose this over createClarityDocumentUploadUrl or createClarityTeamDocumentUploadUrl, and no mention of the required follow-up step (completeClarityOrganizationDocumentUpload). Usage is only implied by the phrase 'organization-level'.

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