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

The description adds useful behavioral context beyond the readOnlyHint and idempotentHint annotations by specifying that only non-secret data is returned and by naming the output dimensions: freshness, state, and active/stale counts. It does not contradict the annotations and gives enough behavioral nuance for a no-argument read-only call.

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 with no filler. Every term — 'non-secret', 'synchronization freshness', 'state', 'active/stale counts', 'approved organic sources' — adds meaningful 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?

With zero required parameters, an output schema available, and annotations covering read-only and idempotent behavior, the description provides a complete invocation contract. Nothing critical is missing for an agent to call this tool correctly.

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?

There are zero parameters and schema description coverage is 100% vacuously, so no parameter documentation is needed. The description focuses on the return payload instead, which is appropriate for a parameterless tool.

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 uses a specific verb ('Return') and a precise resource: synchronization freshness, state, and active/stale counts for approved organic sources. The aggregate 'counts' language distinguishes it from sibling tools like inspect_organic_resource, which implies per-resource inspection. This makes the tool's purpose immediately clear.

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 this is the tool for querying aggregate organic-source status, but it never explicitly states when to use it versus siblings like inspect_organic_resource or validate_organic_resource. There are no exclusions or alternative routing hints, though the scope is reasonably inferable from the title and description.

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