render_endnotes

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. It states it 'renders' and 'creates' a section but does not disclose whether the action is destructive, reversible, or modifies the document permanently. The return type is vague ('Success or error message'), lacking specifics on outcome.

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 a return line, front-loaded with the core action. Every sentence is necessary and no extraneous 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 tool with no parameters, the description is somewhat complete but lacks details on whether it modifies the current document, if it can be called multiple times, or if there are side effects. The existence of an output schema is noted but not used to explain return values beyond 'Success or error message'.

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 tool has zero parameters, and schema coverage is 100% (empty schema). Description adds no parameter meaning but baseline is 4 for 0 params; it does not need to add value here since there are no 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 tool renders all endnotes at the end of the document and creates an 'Endnotes' section with numbered entries. This distinguishes it from sibling tools like add_endnote which add endnotes rather than render them.

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?

No guidance on when to use this tool, prerequisites (e.g., must have endnotes in the document), or conditions where it should not be used. The description provides no context for an agent to decide when to invoke this tool over others.

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