reinforce_concept

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

With no annotations provided, the description carries the full burden of disclosing behavior. It explains the action (strengthening confidence) but does not mention side effects, reversibility, permissions, or the effect on existing confidence values. This is a significant gap for a state-modifying tool.

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 well-structured, front-loading the main purpose followed by clear Args and Returns sections. Every sentence adds value without unnecessary verbosity.

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's low complexity (2 params, no nested objects) and the presence of an output schema, the description adequately covers the core functionality, usage context, and return message. It could strengthen completeness by noting error conditions or idempotency, but it is generally sufficient.

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?

Schema description coverage is 0%, so the description must compensate. It explains concept_id as 'The concept ID to reinforce' and evidence as 'Description of the confirming evidence,' adding meaningful semantic context. However, it does not note that evidence is optional (has a default) or clarify the expected format of evidence beyond 'description.'

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 uses the specific verb 'Strengthen' with the resource 'a concept's confidence in the knowledge graph,' clearly distinguishing it from sibling tools like merge_concepts and retract_node. It states exactly what the tool does.

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 provides explicit when-to-use guidance: 'Call this when a concept is confirmed during conversation, or when new evidence supports an existing concept.' It does not mention alternatives or when not to use, so it stops short of a full 5.

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