tracker_add

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

With no annotations, the description carries the full burden of behavioral disclosure and does little with it. It is clearly a write operation, but it never says whether duplicates are rejected or merged, whether the URL is validated, what the tool returns, or whether entries can be undone; only the enum lists add real content.

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 with the purpose front-loaded and the constrained values listed compactly as pipe-separated sets. No filler, no repetition of the tool name, nothing that could be cut without losing 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?

For a six-parameter write tool with no annotations and no output schema, the definition covers the core action and the two enum-constrained fields but is silent on return behavior, deduplication, validation, and the meaning of the contact/notes fields. It is callable but an agent would be guessing about side effects.

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% and the schema declares kind and status as bare strings with no enums, so the description's enumerated allowed values for those two parameters add substantial meaning the schema lacks. However, url, site, notes, and contact get no guidance at all — no domain-vs-sitename convention, URL format, or notes/contact intent — so half the surface remains undocumented in both places.

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 opens with a specific verb and resource: 'Add a backlink opportunity to the tracker', which is immediately distinguishable from tracker_update and tracker_list by the word 'Add'. It does not explicitly contrast itself with siblings like qualify_prospect or tracker_update, but the create-vs-update-vs-list split is inferable from the names.

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?

There is no when-to-use guidance: nothing says to call this instead of tracker_update, or whether qualify_prospect should precede adding an entry. No prerequisites, no mention of duplicate handling, and no statement about when-status should be set at creation rather than updated later.

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