register_concept

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds context that the tool is a write operation for registering new concepts. However, it does not detail side effects, idempotency (idempotentHint=false), or data persistence, missing opportunities to fully disclose behavior beyond annotations.

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 concise and front-loaded, stating the core purpose first. Every sentence adds value—defining the key constraint on description and clarifying optional fields. No wasted words.

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?

Given the tool has 4 parameters (1 required) and an output schema (not shown), the description covers the purpose and each parameter well. It does not explain return values, but the output schema likely handles that. Overall, it is sufficiently complete for a registration tool.

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?

With schema coverage at 0%, the description compensates fully by explaining each parameter: description should use examples (not labels), triangulation_notes as paraphrase runs, and confidence with enumerated values. This provides essential semantics that the schema alone does not.

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 'Register a concept that lacks a precise human name,' using a specific verb and resource. It distinguishes from siblings like concept_manage (managing existing concepts) and expand_concept (expanding concepts), making the purpose unambiguous.

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 implies usage for concepts without a precise human name but does not explicitly state when to use this tool versus alternatives like concept_manage or expand_concept. No contrast or exclusions are provided, leaving it to the agent to infer context.

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