add_triple

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

The description discloses auto-creation behavior: 'Entities are auto-created by name if they don't exist'. It also notes the return format as JSON string. Annotations provide destructiveHint: false, which aligns with a create operation. No contradictions.

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 very concise: a one-sentence summary followed by a simple argument list and return statement. Every sentence serves a purpose, no fluff.

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 low complexity (3 string parameters, no enums, output schema exists), the description covers the essential aspects: purpose, parameters, return format, and auto-creation. Could mention potential errors but adequate.

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 has 0% description coverage, but the description adds one-sentence definitions for each parameter: 'The subject entity name', 'The relationship predicate', 'The object entity name.' These add some meaning beyond the titles but are minimal.

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 action: 'Add a knowledge graph triple (subject -> predicate -> object)'. It distinguishes itself from siblings like 'query_triples' by focusing on creation rather than retrieval.

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 an implied usage context (adding triples) but does not explicitly state when to use this tool versus alternatives like query_triples for retrieval. No exclusions or prerequisites are mentioned.

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