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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains that the result contains one entry per ingest delta, lists the included fields (job, triple count, timestamp), and states the ordering is newest first. This gives a clear picture of what the tool returns, though it does not mention authentication or error 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 a single, front-loaded sentence that efficiently communicates the resource, the nature of the entries, and the ordering. Every word contributes value, and there is no wasted content.

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 simple read-only history tool with one parameter and no output schema, the description supplies sufficient contextual detail: what each entry contains and the sort order. It stops short of specifying the exact return envelope or pagination, but these are not strictly necessary for basic 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?

The schema has only one required parameter, named_graph_iri, with no description. The tool description indirectly clarifies this parameter by stating the tool operates on 'a named graph', so the meaning of the parameter is inferable. However, it does not explain IRI format or constraints, and at 0% schema coverage more explicit compensation would be beneficial.

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 identifies the tool's function: returning change history for a named graph, with one entry per ingest delta. It specifies the entry contents and ordering, making it distinct from other history/provenance tools, though it lacks an explicit verb.

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 implies the tool is for inspecting the ingest delta history of a named graph, but it does not explicitly state when to choose this over siblings like brainkb_delta_compare or brainkb_provenance_graph. There is no exclusion or alternative guidance.

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