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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds useful context beyond annotations by specifying the object of the check ('connector grants and secrets') and the source ('gateway'), which helps set expectations without contradicting any annotations.

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 a single, front-loaded sentence of nine words. Every word contributes meaning, with no filler or redundant detail. It is an model of conciseness.

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?

With no parameters and an output schema present, the description is largely sufficient. It tells the agent what the tool does and from where. The only minor gap is that 'secrets status' could be slightly ambiguous, but the output schema likely mitigates this. Overall, it is complete for the tool's simplicity.

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 tool has zero parameters, so the schema covers everything. The rubric gives a baseline of 4 for 0 parameters, and the description does not need to add parameter details. It correctly focuses on the action and scope.

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 ('Check') and clearly identifies the resource ('connector grants and secrets status') and origin ('from the gateway'). This distinguishes it from sibling tools like thinkneo_rotate_key (which mutates) and thinkneo_cache_status (which checks a different resource).

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 this tool is used when you need to inspect the status of connector grants and secrets, but it provides no explicit guidance on when to prefer it over alternative tools or any exclusions. With many sibling tools, more explicit context would be helpful, but the basic usage scenario is clear.

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