Blame an entity

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

Annotations declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating safety. The description adds valuable behavioral details: it returns the most recent change details and, if no history exists, returns a JSON error object with protocol-level isError: false. This goes beyond 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?

The description is two sentences with no filler. It front-loads the core purpose (what, when, who, why) and uses a familiar analogy (git blame). Every word serves a purpose.

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?

The tool has only one parameter with thorough schema documentation and an output schema exists. The description covers the core functionality and error behavior adequately within its scope, leaving no gaps for this simple tool.

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 100%, and the schema already provides examples and exact path requirements. The tool description does not add additional parameter information, so baseline score of 3 is appropriate.

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 states the tool retrieves the most recent change to an entity, specifying what changed, when, who, and why. It uses the analogy of 'git blame' and explicitly mentions the types of entities (DB columns, functions, etc.), making its purpose unmistakable and distinguishing it from siblings like 'history' or 'diff'.

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 usage for viewing the latest change, and the mention of returning an error if no history exists provides context. However, it does not explicitly state when to use this tool over siblings like 'history' (which might return all changes) or 'diff', nor does it specify prerequisites or when not to use it.

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