list_concepts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It simply says 'list concepts' with no information about side effects, read-only nature, rate limits, pagination, or return format. The agent has no idea what to expect.

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?

While the description is extremely short (two words), this is not effective conciseness—it is under-specification. There is no front-loaded key information; the description provides no value whatsoever. A concise description of one useful sentence would be far better.

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?

This is a 9-parameter tool with no output schema, no annotations, and no documentation. The description is entirely inadequate for an agent to call it correctly. It does not explain what a concept is, how the parameters relate, or what the return value looks like.

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 schema has 9 parameters and 0% description coverage. The description adds no meaning to any parameter. The agent cannot infer what 'domain_id', 'concept_id', 'snapshot_id', 'request_id', or 'tool_version' mean in this context. The description completely fails to compensate for the missing schema documentation.

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 'list concepts' is a tautology that simply restates the tool name. It does not specify what a 'concept' is, what resource is being listed, or how it differs from sibling listing tools like list_scopes, list_domains, or list_contexts. An agent cannot distinguish this tool from its siblings.

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 or when to prefer alternatives. No context, prerequisites, or examples are provided. The agent is given zero help in selecting this tool over the many similar list/read tools.

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