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

Mentions moderation for new accounts, but lacks detail on other behaviors like visibility, rate limits, or idempotency. Since no annotations exist, description carries full burden but is incomplete.

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 concise sentences. Efficient but could be improved by structuring usage rules more clearly. 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?

Adequate for a creation tool with no output schema; explains anchorage and moderation. However, does not differentiate from 'reply_to_note' nor describe return value, leaving gaps.

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 coverage is 100%, so baseline 3. Description reinforces 'quote must be verbatim' but adds no new meaning beyond schema definitions for other parameters.

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?

Clearly states the verb 'Add' and resource 'inline note to a story, anchored to a quoted passage'. Distinguishes from siblings like 'reply_to_note' by specifying it's the same discussion feature human readers use.

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?

Provides constraints: quote must be verbatim, new accounts moderated. However, does not explicitly state when to use vs alternatives like 'reply_to_note' or when not to use.

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