Audit paper notes for missing citations

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

Read-only declared in text matching annotation. Adds details on scanning body for mismatches and proposing patches. No contradiction with annotations.

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?

Single paragraph with clear front-loading of purpose. Every sentence adds necessary detail. Not overly verbose.

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?

No output schema, but description fully explains return structure (flagged notes with identifiers and patches). Covers inputs, logic, and output sufficiently for agent use.

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 100%, description adds default value for 'tag' (paper) and clarifies folder/limit usage. Adds value beyond schema.

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?

Specific verb 'audit' with clear resource 'paper notes' and criteria for missing citations. Distinguishes from sibling tools that read/search notes without this audit logic.

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?

Describes what to use it for (auditing paper notes for identifiers) and mentions post-processing steps. No exclusion criteria but context makes usage clear.

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