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

The description is consistent with the readOnlyHint=true annotation, which is good. Beyond that annotation, it adds an important behavioral fact: the fetch is bound to the active Space unless space_id is supplied, plus the override allows reading another Space without changing the session binding.

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?

Two tight sentences put the primary action first, then a single sentence covers Space-scoping, switching, and the per-call override. There is no filler or redundant restating.

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 simple single-fetch operation with two parameters and no nested objects, the description covers the required concept_id, the consequential Space-scoping, and the override path. An agent has everything necessary to invoke it correctly, despite the lack of an output schema.

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 fully documents space_id but leaves concept_id as a bare string; '...by id' in the description adds some meaning, clarifying that concept_id is the lookup key. It does not give any formatting or type guidance beyond that, so it's helpful but not comprehensive.

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 opens with 'Fetch one concept by id,' which states a specific verb, a clear resource, and the primary lookup criterion. This decisively distinguishes it from list_concepts, create_concept, update_concept, and delete_concept, even without naming them.

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?

It clearly says the tool reads a concept in the active Space and points to set_active_space as the way to switch Spaces, with space_id as an optional one-call bypass. It gives solid context for when to call this vs. switching Spaces, although it doesn't explicitly name list_concepts as an alternative for multi-concept fetches.

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