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

There are no annotations, so the description carries the full burden of behavioral disclosure. It adds one important authorization fact—platform access is separate from tenant ownership—but it does not disclose what the tool returns, whether it errors or returns false when the caller lacks platform access, or any session/authentication requirements. For a context-check tool, this is a significant 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?

The description is only two sentences, both of which earn their place. The core purpose is front-loaded, and the second sentence adds a crucial scope restriction without any wasted words.

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 is very simple—zero parameters and no nested schema—so the description doesn't need much. Still, with no output schema and no annotations, it should at least state whether the tool returns a boolean confirmation, a role value, or raises an error when platform access is absent. The existing caveat about tenant ownership is helpful but not enough to fully close that gap.

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 input schema is empty and no parameters exist, so the description has no parameter semantics to explain. The explicit empty schema already makes the no-argument call contract clear, which is worth a baseline of 4.

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 a specific action and resource: 'Confirm the caller's platform role.' It also distinguishes platform access from tenant ownership, which helps separate it from sibling context tools like commsharbor_context. However, it doesn't explain what 'platform role' concretely is (role name, boolean, access level), so it stops short of a 5.

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 when to use it: whenever the caller's platform role needs confirmation. The warning that 'Tenant ownership grants nothing here' provides useful when-not-to-assume guidance. But it doesn't name alternatives such as commsharbor_context or commsharbor_me, nor does it state explicit conditions for choosing this tool over them.

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