submit_collection_content

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it describes the two-step process (upload to GitHub portfolio, then create submission issue), specifies it handles 'all content types including personas', and implies it requires GitHub authentication (though not explicitly stated). It doesn't mention error handling, rate limits, or response format, but provides substantial operational context beyond basic functionality.

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?

The description is perfectly structured and concise: three sentences that each earn their place. The first states the core action and two-step process, the second provides usage guidance, and the third clarifies content type handling. No wasted words, and the most critical information (what the tool does) is front-loaded.

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 single-parameter tool with no annotations and no output schema, the description provides excellent context: it explains the submission workflow, content type handling, and usage scenario. The main gap is lack of information about response format or error conditions, but given the tool's relative simplicity and good parameter documentation, it's nearly complete for agent understanding.

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% for the single parameter 'content', but the description adds valuable semantic context: it explains that for personas, the content should be 'the persona's name (e.g., 'Creative Writer') or filename' and that 'The system will recognize it as a persona based on its metadata.' This clarifies usage beyond the schema's basic description of 'The content name or filename to submit.'

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?

The description clearly states the specific action ('Submit a single element TO the DollhouseMCP community collection'), identifies the resource ('element'), and distinguishes it from siblings by specifying it's for sharing custom elements with the community via GitHub portfolio submission. It explicitly mentions handling 'all content types including personas', which differentiates it from more specific tools like 'import_persona' or 'create_element'.

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?

The description provides explicit guidance on when to use this tool: 'Use this when users want to share their custom elements with the community.' It also distinguishes from alternatives by specifying the two-step process (upload to personal GitHub portfolio, then create submission issue), which contrasts with tools like 'install_collection_content' or 'browse_collection' that don't involve submission workflows.

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