notion_oauth_revoke

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

With no annotations, the description fails to disclose behavioral traits such as whether revocation is irreversible, what permissions are required, or any side effects. It only mentions routing details, which do not inform the agent of the tool's impact.

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 very short but at the cost of essential information. It is under-specified for a tool performing a sensitive action like OAuth revocation. Every sentence should add value; here the routing detail is trivial.

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 and importance (revoking authentication), the description is highly incomplete. It does not cover prerequisites, success/failure conditions, or what happens after invocation. The output schema exists but does not compensate for lack of contextual guidance.

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?

The sole parameter 'arguments' is described as a 'JSON string of arguments for the connector operation' but no further details are provided. Schema coverage is 0%, and the description does not list expected keys or formats, leaving the agent unable to construct a valid argument.

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 is for 'oauth_revoke' operation on Notion, which implies revoking OAuth tokens. However, it does not explicitly state what is being revoked (e.g., user access token, refresh token) and does not differentiate from sibling tool 'notion_oauth_introspect'.

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?

No guidance on when to use this tool versus alternatives like 'notion_oauth_introspect'. There is no mention of prerequisites, context, or exclusions. The AI agent is left guessing about appropriate invocation scenarios.

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