camelot_social_media_planner

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the agent knows this is a non-destructive, repeatable operation. The description adds 'Local browser processing' and a canonical URL, which provide some behavioral context beyond the annotations, but it doesn't detail what happens to the generated content or whether it persists.

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 compact and front-loaded with the core purpose. The 'Local browser processing' and canonical URL add useful context without bloating the text. The trailing double period is a minor formatting flaw but doesn't hurt clarity.

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?

Given the tool has an output schema, all parameters are documented, and annotations cover the safety profile, the description is reasonably complete. It could benefit from a note about what the output looks like or how the scheduling works, but the essential information for an agent to select and invoke the tool is present.

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%, so the schema already documents all three parameters (brandName, campaignTheme, targetChannels). The description adds no additional parameter-level meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 states a specific verb ('Plan and schedule') and resource ('multi-channel social media content calendars with draft posts'), which clearly distinguishes it from the sibling tools. It doesn't explicitly name a sibling alternative, but the function is clear enough that an agent can tell it apart from the other Camelot tools.

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 implies usage for planning and scheduling social media content, and the 'Local browser processing' note gives some context. However, it doesn't explicitly state when to use this tool versus alternatives like camelot_ad_copy_template_builder or camelot_email_campaign_writer, nor does it provide exclusions or prerequisites.

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