Citizen Deployment MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It effectively communicates critical behavioral traits: this is a prerequisite operation that must be called first, it returns instructional content rather than performing actions, and following its output is mandatory for subsequent operations. However, it doesn't specify response format, error conditions, or authentication requirements.

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 appropriately sized and front-loaded with the most critical information ('CRITICAL: Call this FIRST before ANY deployment operation'). Every sentence earns its place by establishing importance, describing the return value, and specifying usage requirements. The structure could be slightly more concise by combining some of the deployment tool references.

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's complexity (prerequisite instructional tool) with no annotations and no output schema, the description does well to establish critical context: sequencing requirements, purpose, and relationship to sibling tools. However, without an output schema, it doesn't fully describe what the instructions contain or their format, leaving some ambiguity about the return value.

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?

The tool has 0 parameters with 100% schema description coverage, so the baseline would be 4 even with no parameter information. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's purpose and usage requirements.

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 tool's purpose with specific verbs ('Call this FIRST', 'Returns deployment instructions') and resources ('deployment instructions including polling intervals, error handling guides, and best practices'). It explicitly distinguishes this from sibling tools by naming specific alternatives (deploy_from_git, deploy_from_local, get_deployment_status) that should only be called after this one.

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 usage guidelines: 'Call this FIRST before ANY deployment operation' establishes clear precedence, and 'You MUST read and follow these instructions before calling deploy_from_git, deploy_from_local, or get_deployment_status' names specific sibling tools with explicit sequencing requirements. This gives comprehensive when-to-use guidance with clear exclusions.

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