noetic.deny_request

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

No annotations are provided, so the description must fully disclose behavior. It mentions owner-governed but does not state whether the request is permanently deleted, whether it can be reversed, or whether an admin can act on behalf of the owner. Lacks authorization failure handling and side-effect details. This is a significant gap for a denial action.

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 short and to the point, with the action and ownership condition front-loaded. It is not wasteful, though it could be more complete without becoming lengthy. Slightly more detail on behaviors or parameters would not hurt.

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?

For a tool with no annotations stub and no output schema, the description is too sparse. It omits key context: how to obtain requestId (likely from list_requests), what sessionId is used for, and post-denial effects. The sibling list provides some context but not enough for correct usage.

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?

With 0% schema description coverage and no parameter descriptions, the agent is left without any explanation of what requestId and sessionId represent or where to find them. The description does not compensate, despite the schema providing only bare type declarations. This forces agents to guess or make errors.

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 action (deny), the resource (pending access request), and the ownership condition (space you own). It is distinct from its siblings approve_request, list_requests, and request_access, and the one-line summary is sufficient to understand its role.

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 it should be used for pending requests, but it does not explicitly state when to use it versus approve_request or list_requests. It also omits prerequisites like the need for an active session or ownership verification, which is moderately important given transactional context.

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