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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'static risk brief' implying read-only analysis, but does not explicitly say it makes no external calls, that it's synchronous, or what side effects might occur. It also doesn't disclose whether network access is required or what happens with invalid inputs. Given no annotations, this is a meaningful 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?

Single sentence, front-loaded with purpose, zero fluff. Efficiently communicates the tool's function and output categories.

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?

No output schema, low param coverage, description focuses on purpose/output but not on how to use parameters or what constraints exist. Missing guidance on which input to provide (server vs openapi vs manifest), or what 'static' means for the agent.

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 coverage is low (~38%), with only 3 of 8 params having schema descriptions. The description lists output contents but provides no guidance on how to choose between server_url, openapi_json, and tool_manifest inputs, or how sensitive_context and intended_task should be populated. Description doesn't compensate for missing param docs.

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?

Description clearly states the tool produces a static risk brief for MCP servers, OpenAPI specs, or tool manifests, and lists the output categories (tool risk, PII, credentials, policy). This is specific verb+resource+scope. It distinguishes from sibling tools like mcp_approval_pack and agent_security_policies by emphasizing a pre-connection risk brief.

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 timing context ('before an agent connects it') which helps the agent know when to use it. However, there is no mention of when NOT to use it or alternatives among siblings like mcp_approval_pack or check_agent_policy. The guidance is adequate but not explicit about exclusions or trade-offs.

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