list_agent_configs

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

With no annotations, the description carries the full disclosure burden, yet it never confirms this is a read-only/non-mutating operation, nor whether it requires a running agent session, nor what the result contains. 'Discover' implies a lookup but nothing about caching, side effects, or scope is stated.

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?

A single compact sentence with no filler and no repetition of the title. It is front-loaded on the verb, though the trailing noun list reads as an unstructured enumeration rather than prioritized information.

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?

For a zero-parameter read tool with no output schema, the description should at least frame what comes back; the four enumerated item types gesture at the return payload but remain undefined terms ('pinned options', 'backend capabilities'). It is minimally adequate but leaves the agent guessing about the result shape.

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 the schema baseline of 4 applies and there is nothing for the description to disambiguate. No parameter-related gap exists.

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 verb 'Discover' plus an enumerated list of item kinds gives a rough idea that this returns available configuration/capability information, but the phrasing 'callable configs, source files, pinned options and backend capabilities' is a grab-bag that never says what a 'config' is or what relation it has to agents. It does not distinguish itself from siblings such as list_models or list_agents, which an agent could easily confuse with it.

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 statement of when this tool should be called, no prerequisites, and no reference to any alternative among the many sibling list_* tools. The agent must infer usage from the name alone.

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