AAP 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 mentions 'proper authentication' which is useful context, but doesn't describe rate limits, error handling, response formats, pagination, or what happens with destructive operations like DELETE. For a generic API tool that could perform any operation, this lack of behavioral context is a significant gap.

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 with a clear purpose statement followed by helpful examples. Each example demonstrates a different use case efficiently. The structure is front-loaded with the core functionality, though the examples section is somewhat lengthy for a description.

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 (generic API access with 4 parameters) and the presence of an output schema (which means return values are documented elsewhere), the description is moderately complete. It covers the basic purpose and provides usage examples, but lacks important behavioral context about authentication details, error handling, and when to use versus specialized siblings, which is crucial for a tool of this nature.

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 parameters thoroughly. The description adds value through concrete examples showing how parameters combine (e.g., GET with params, POST with data), which helps understand parameter semantics beyond individual descriptions. However, it doesn't add significant new semantic information beyond what the schema provides.

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 provides 'direct access to any AAP Gateway API endpoint with proper authentication', which is a specific verb+resource combination. It distinguishes itself from sibling tools by being a generic API access tool rather than domain-specific management tools like 'gateway_service_management' or 'user_access_management'. However, it doesn't explicitly contrast with 'generic_aap_api' which appears to be a similar sibling.

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 context through examples showing when to use GET, POST, etc., but doesn't provide explicit guidance on when to choose this generic tool versus the many specialized sibling tools. There's no mention of trade-offs, prerequisites, or specific scenarios where this tool is preferred over domain-specific alternatives like 'gateway_service_management' for service operations.

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