Who am I

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

With no annotations provided, the description carries the full burden. It explains the data source (HYPERPANES_PANE_ID) and the kind of information returned, but does not explicitly state whether the operation is read-only, if any permissions are needed, or what happens if the paneId is invalid. It implies non-destructive behavior but lacks explicit disclosure.

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 concise: two sentences, front-loaded with the primary action, and every phrase contributes (mechanism, reported fields, use case, optional parameter). No filler.

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 no output schema and no annotations, the description compensates by listing the reported metadata fields and explaining the main use case. It does not describe error behavior or return format in detail, but for a simple read-only introspection tool it provides sufficient context for an agent to invoke it appropriately.

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 only parameter (paneId) is described as optional and for 'a specific pane instead', which adds meaning beyond the bare schema. However, it does not detail format, validation, or default behavior beyond 'instead', so it is clear but not exhaustive.

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 ('Identify') and resource ('the pane this MCP bridge is running inside'), and clearly states what it reports (org metadata + window/tab context). It also provides a practical use case as 'the recursion enabler', distinguishing it from sibling tools like list_panes or read_pane.

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 gives a clear scenario for when to use it: 'a manager-agent-in-a-pane calls this to learn who it is before driving its sub-workers.' It also explains the optional paneId usage ('describe a specific pane instead'). It does not explicitly mention when not to use it or list alternatives, but the context is clear.

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