forcepoint_mcp_http_token_get

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

With no annotations, the description carries the full burden. It discloses 'Read-only' and the Vault storage context, which is useful, but omits details like response format, pagination, or behavior when userId is absent. The read-only note adds value, but more transparency would be expected.

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?

A single, well-structured sentence with no redundancy. It is front-loaded with the verb and resource, making it easy to parse.

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 description lacks return-value details (no output schema) and does not specify criteria for when to use this tool over other token-related siblings. With zero annotations and no output schema, more context is needed to be complete.

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%, so the description must compensate. It says 'user-scoped,' hinting that userId filters by user, but does not explain the parameter meaning, optionality in prose, or behavior when omitted. This is insufficient for an agent to understand how to set the parameter.

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 uses a specific verb 'List' and identifies the resource 'user-scoped MCP HTTP bearer-token metadata stored in Vault,' clearly distinguishing it from mutation siblings like upsert/revoke. The scope and data source are explicit.

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 (listing token metadata) but does not explicitly state when to prefer it over forcepoint_user_token_get or other siblings, nor does it mention exclusions or prerequisites. It gives no direct comparison to alternatives.

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