execute

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

With no annotations, the description fully carries the behavioral disclosure burden. It states the MCP runs remotely, cannot access the user's filesystem, and requires the client to send file content via sourceFiles. It also discloses side effects such as publishing to Azure Storage and writing reports to a database.

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 long due to covering eight actions, but it is well-structured with a lead paragraph and bullet list. It front-loads the critical remote-execution context and uses efficient formatting, though some redundancy exists (e.g., repeating the action list in the schema) that could be trimmed.

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 high complexity (8 actions), the absence of output schema and annotations, the description is remarkably complete. It covers workflow, authentication, file handling, action-specific parameters, and side effects, providing everything an agent needs to select and invoke the correct action.

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 only defines generic action and params fields, but the description details per-action parameter structures, including required and optional fields like sourceFiles, siteName?, and skipBuild?. This adds significant meaning beyond the bare schema, particularly the note that sourceFiles must contain content, not paths.

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 identifies the tool as a unified documentation MCP for Satrack and enumerates eight specific actions, each with a distinct verb (get, generate, publish, report). It effectively distinguishes between these internal operations and makes the tool's purpose unambiguous.

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 workflow instructions: call get_documentation_rules first, use the agent's own tools to read files, and write outputs locally. It also clarifies when each action is applicable and gives authentication guidance for get_user_info, offering strong usage direction in the absence of sibling tools.

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