get_concepts

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds 'concise' regarding response nature and mentions no mutation capability, but the latter is redundant with the annotations and adds limited additional behavioral context.

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 brief and front-loaded with the read-only nature and the core action. The phrase 'It exposes no mutation capability' is somewhat redundant with 'Read-only', which slightly reduces efficiency, but overall the description is well-sized.

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-only tool with an output schema, the description is largely sufficient. It identifies the key result categories (current, affected, historical) and safety profile. It could be more complete by stating when to prefer this over sibling read tools, but the simplicity of the tool lowers that burden.

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?

There are no parameters, and schema description coverage is 100% (empty schema), so the description carries no obligation to explain parameters. The baseline of 4 applies here since the tool has no parameters to document.

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 clearly states the tool returns concise current, affected, and historical engine concepts, which is a specific verb and resource. It does not explicitly differentiate itself from siblings like get_state or get_round, so it falls short of a 5.

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?

The description gives no guidance on when to use this tool versus alternatives such as get_state, get_round, or get_unresolved. It only states what the tool does, not the conditions or context that should lead an agent to choose it.

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