add_user_topic

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

Without annotations, the description carries full behavioral disclosure burden but only says 'Add a topic to track for new publications.' It does not mention side effects (e.g., overwrite existing topic), required permissions, rate limits, or any behavioral constraints. The uniqueness hint in the param description is about parameter validation, not tool behavior.

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: two lines of purpose and two parameter lines. It is front-loaded with the primary action, and every sentence adds value. There is no redundant or tangential information.

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 relative simplicity and the existence of an output schema (not shown), the description covers the core add operation. However, it omits context like whether topics persist across sessions, any maximum limits, or connection to the publication tracking system. It is adequate but not comprehensive.

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 input schema has 0% description coverage, so the description fully compensates by explaining each parameter: 'topic' is uniquely named, 'description' is optional for search criteria. This adds meaningful semantics beyond the schema's bare type definitions.

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 tool adds a topic to track new publications. It uses a specific verb ('Add') and resource ('topic'), with a clear purpose. The context for new publications distinguishes it from other 'add_' sibling tools like add_glossary_term or add_journal_entry.

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 does not provide explicit guidance on when to use this tool versus alternatives. It lacks any mention of prerequisites, when not to use it, or comparison to sibling tools that might also manage tracked items.

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