List Admin About Check

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Check App Config' does not state whether this is read-only, whether it triggers diagnostics, what auth is required, or what side effects might occur. The mismatch between the list_ prefix and the verb 'check' further obscures the 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?

Three words is under-specification rather than concision. The single sentence adds almost no usable information and has no structure or front-loaded detail that helps an agent act. It fails to earn its place as a tool description.

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?

Although an output schema exists, the description does not explain what 'App Config' covers, what 'check' means, or how this tool relates to the many admin/about sibling tools. An agent cannot reliably decide when to call this tool based on the provided context.

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?

Schema description coverage is 0%, and the description does not mention the accept-language parameter at all. The agent gets no explanation of how this optional header affects the request or the response. The description adds no meaning beyond the raw schema property name.

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 says only 'Check App Config', which uses a generic verb and a vague resource. It does not say what a 'check' entails or what the tool returns, and it does not distinguish this from siblings like list_admin_about, list_admin_about_statistics, or list_app_about. The name suggests 'list' while the description says 'check', leaving the action ambiguous.

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?

There is no guidance on when to use this tool versus any alternative. It never mentions prerequisites, intended scenarios, or when a sibling tool should be preferred. An agent must infer usage context entirely from the name and title.

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