codex_app_mcp_call

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly states that the tool is disabled until allowlists are configured, which is essential operational knowledge. However, it does not disclose other behavioral aspects such as authentication requirements, error handling, or side effects, leaving significant gaps.

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 extremely concise: two sentences, both front-loaded with critical information. The first sentence states the core action, and the second provides an important operational constraint. Every word earns its place, with no fluff or redundant detail.

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?

The tool has 5 parameters, nested objects, no output schema, and no annotations. The description only covers the tool's general purpose and one restriction, leaving out essential context such as expected argument structure, return values, and error scenarios. This is inadequate for a tool of this complexity.

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 0%, and the description provides no information about the parameters (server, tool, arguments, threadId, _meta). The agent is left without any guidance on how to fill the required fields, making parameter usage completely opaque. The description does not compensate for the schema's lack of detail.

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's purpose with a specific verb ('Call') and resource ('an explicitly allowlisted downstream MCP/SaaS tool through app-server'). It clearly differentiates from sibling tools by focusing on downstream tool invocation. The phrase 'explicitly allowlisted' adds necessary context about the tool's scope, though it doesn't explicitly name alternatives.

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 a clear prerequisite ('Disabled until server and tool allowlists are configured'), which is useful guidance for when the tool can be used. However, it does not explain when to choose this tool over sibling alternatives, nor does it mention any fallback or excluded use cases. The guidance is implied rather than explicit.

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