ghl_location_upload_file_custom_fields

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

Adds context about the multipart format and no JSON alternative, beyond annotations. But omits details on success/error responses, file size limits, or other behavioral traits that would fully inform the agent.

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 concise: two sentences plus endpoint and scopes. Critical info is front-loaded, no unnecessary words.

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?

Covers essential aspects (purpose, content type, endpoint, scopes), but lacks output schema details, error handling, and file constraints. Adequate but not comprehensive.

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?

Description clarifies that the body contains 'the file plus its associated customField id/name', which is not evident from the schema alone. Schema has 'id' and 'maxFiles' but 'customField id/name' is added meaning.

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?

Clearly states 'Uploads File to customFields' and specifies the endpoint. However, it does not distinguish from similar upload tools like ghl_form_upload_custom_files or ghl_media_upload_file, relying on the endpoint and name for differentiation.

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?

Explicitly states that the body must be multipart/form-data and not JSON, and provides OAuth scopes. However, it lacks guidance on when to use this tool versus alternatives or when not to use it.

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