add_user_topic

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

No annotations are provided, so the description must fully disclose behavior. It does not mention uniqueness enforcement (though hinted in parameter docs), idempotency, permissions, or side effects. The output schema exists but is not described, leaving behavioral gaps.

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 sentences plus parameter list, front-loaded with purpose. No redundancy, every word serves a purpose.

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 add tool with 2 parameters and no annotations, the description is adequate but incomplete: no return value explanation, no error conditions, and limited behavioral context. Could be more informative.

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?

Description repeats parameter names and adds minimal context: 'unique' for topic and 'optional description of what to look for' for description. With 0% schema coverage, it compensates partially but lacks examples or format details.

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') and the resource ('a topic to track for new publications'), using a specific verb and resource that distinguishes it from sibling tools like add_glossary_term or add_memory_entry, which have different purposes.

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 the tool is for tracking publications but does not explicitly state when to use it over alternatives or provide exclusion criteria. No mention of when not to use it or related tools.

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