Select current site

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

The description adds important behavioral context not in annotations, such as 'Persists across MCP restarts.' This clarifies the stateful mutation effect, complementing the readOnlyHint=false annotation, though it could mention the result of overwriting a previous selection.

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 three concise sentences with front-loaded action ('Sets the current site'), followed by persistence and a prerequisite. Every sentence earns its place with no 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?

For a simple state-setting tool with one parameter and an output schema, the description covers the purpose, necessary prerequisite, and persistence behavior. It is sufficiently complete for an agent to use the tool correctly.

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 schema already provides full meaning for site_id ('PushEngage site_id from pushengage_list_sites'). The description references the parameter but does not add new semantic detail beyond what the schema covers, so it meets the baseline.

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 it 'Sets the current site' used by all site-scoped tools, and explicitly lists example tools. This specific verb+resource combination distinguishes it from siblings like pushengage_list_sites.

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?

It explicitly instructs to call pushengage_list_sites first to get a valid site_id, and explains when the selection applies ('when no site_id is provided'). This gives clear, actionable usage context for the agent.

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