List Admin About

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

No annotations are provided, so the description carries full responsibility for behavior disclosure. It indicates a read operation via 'Get' but does not mention admin requirements, authentication, localization behavior, or any other operational details. It does not contradict annotations, but it reveals very little beyond the basic operation.

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 short sentence with no filler, making it efficient and front-loaded. It is concise, though the brevity borders on under-specification.

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 simple, has an output schema, and has only one optional parameter, so return values are covered elsewhere. However, in a large sibling set with similar about-tools, the vague 'general application information' does not clarify scope or selection, and there are no annotations to fill the gap. It is minimally adequate but incomplete.

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, accept-language, is not mentioned in the description, and schema description coverage is 0%. The description adds no meaning beyond the schema, forcing the agent to infer the parameter's purpose solely from its 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 states a clear verb ('Get') and a resource ('general application information'). It is understandable but does not differentiate from sibling tools like list_app_about or list_admin_about_check, which could serve similar purposes.

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 alternatives such as list_app_about, list_admin_about_check, or list_admin_about_statistics. The description provides only a generic purpose with no context, exclusions, or selection criteria.

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