AAP MCP Server

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

No annotations are provided, so the description carries the full burden. It mentions 'handles' but doesn't disclose behavioral traits such as whether actions are read-only or destructive, authentication needs, rate limits, or error handling. This is a significant gap for a tool with 15 parameters and multiple actions.

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 brief and front-loaded, consisting of two sentences that efficiently outline the tool's scope. However, it could be more structured by explicitly listing key actions or use cases to enhance clarity without adding unnecessary length.

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 complexity with 15 parameters and no annotations, the description is incomplete. It lacks behavioral context and usage guidance, though the presence of an output schema reduces the need to explain return values. This results in a minimal viable but gap-filled description.

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 documents all parameters thoroughly. The description adds no additional meaning beyond the schema, such as explaining parameter interactions or constraints. Baseline 3 is appropriate as the schema does the heavy lifting.

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 the tool handles 'workflow templates, nodes, schedules, and notifications,' which gives a general scope but lacks a specific verb or clear differentiation from sibling tools like 'create_workflow_survey' or 'job_execution_management.' It's vague about what 'handles' entails, making it adequate but not precise.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'create_workflow_survey' and 'job_execution_management,' the description fails to indicate specific contexts, exclusions, or prerequisites, leaving the agent without clear usage instructions.

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