list_admin_about_check

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

No behavioral details are disclosed. The description does not mention read-only status, required permissions, side effects, or what 'check' entails. With zero annotations, the description fails to inform about behavior.

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 extremely concise (two words) but underspecified. It is not front-loaded with useful information and fails to earn its place due to lack of substance.

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 existence of sibling tools and an optional parameter, the description is grossly incomplete. It does not explain what 'check' means, what the output contains, or how this tool fits into the admin about family.

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 single parameter 'accept-language' is not described in the schema (0% coverage) and the tool description does not mention it at all. No additional meaning is provided beyond the schema.

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 'Check App Config' states the resource (App Config) but the verb 'Check' is vague and doesn't distinguish from sibling tools like list_admin_about or list_admin_about_statistics. It barely adds value beyond the tool name.

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 is provided on when to use this tool vs. alternatives. The description lacks any context about prerequisites, context, or scenarios.

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