capabilities

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

Annotations already declare readOnly, closed-world, non-destructive, so safety is covered; the description adds only that the output is "static" (fixed, not computed against live state) and that it includes "limitations," which is mildly useful context. It does not say whether the output is a list, a map of feature flags, or prose, nor whether anything is cached or versioned.

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?

It is short but not concise in the useful sense: a four-word fragment with no subject, verb, or structure, which is under-specification rather than economy. Not a single word is wasted, but the space that was saved is exactly the information the agent needed.

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 output schema, the description carries the full burden of explaining what is returned, and it does so only in the vaguest terms. For an introspection tool whose entire value is its return payload, this leaves the agent unable to predict the response shape or know what "limitations" covers.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. It correctly implies a no-argument call by describing the result rather than any inputs.

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?

"Static capabilities and honest limitations" is a noun fragment that largely restates the tool name and never states a verb or what an agent gets back. It does not distinguish this tool from siblings such as doctor, install_tools, or list_artifacts, so an agent cannot tell from the description alone that this is a self-description/introspection endpoint.

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 call this versus doctor (the closest sibling) or when not to call it, and no indication of preconditions or expected timing. The fragment offers nothing an agent could use to choose between this and the other introspection-style tools.

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