plane-asset-upload

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

Discloses 3-step presigned upload workflow, max file size (5 MB), and supported input formats (file path or base64). No annotations exist, so description carries full burden; it adequately covers key behaviors without contradicting any annotations.

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?

Five sentences, each earning its place: purpose, downstream usage, workflow, constraints. Front-loaded with main action. Zero redundancy.

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 purpose, return value, integration with sibling, process, and constraints. Could mention required parameters (project_id, entity_id) explicitly and elaborate on entity_type options, but overall completes the picture given schema richness.

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 100%, baseline 3. Description adds value by explaining mutual exclusivity of file_path and file_base64, auto-detection of file_name and content_type, and the overall upload process. Enhances understanding beyond schema.

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 'Upload a file to Plane' and 'get an asset UUID back'. Distinguishes from sibling tool plane-page-insert-image which consumes the asset. Provides specific verb and resource.

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?

Describes when to use: to obtain an asset UUID for embedding images via plane-page-insert-image. Mentions the 3-step process. Lacks explicit exclusions or alternatives for file uploads, but context is clear.

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