source_status

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

Read-only hint is given, and the action of re-hashing is explained. However, it does not detail what 'recorded source conclusions' are or the exact nature of the output beyond 'report'.

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?

Three sentences, each adding value: purpose, usage guidance, and read-only hint. No redundant words.

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 check with three booleans and no output schema, the description covers purpose, filters, and use cases. Lacks detail on output format but acceptable for this 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?

Three parameters all have schema descriptions (100% coverage). The description adds semantic context by linking 'changed' and 'missing' filters to stale-source triage, enhancing agent understanding.

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 'check' and resource 'recorded source conclusions' via re-hashing files; differentiates from load_context and other siblings by specifying its role in stale-source triage.

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?

Explicitly states when to use ('full stale-source check beyond load_context') and when not to ('do not repeat when recent load_context, task_audit, or status check answered').

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