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

The description provides valuable operational context by stating it 'runs straight away,' which speaks to latency and performance, a trait not captured in the annotations. It also reinforces its read-only nature and context.

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 definition is extremely concise and efficient. Both sentences are highly functional, front-loading the core functionality before adding context.

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?

Given the presence of an input schema, the definition is robust. It provides all necessary context for an agent to understand the scope of the query. It could be slightly improved by specifying the format of the counts returned.

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?

Since the schema coverage is 100%, the baseline is 3. The description adds contextual reinforcement regarding the site location but does not clarify the meaning or constraints of the parameters beyond what the schema already defines.

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's function: 'Get post counts by status.' It is specific about what is being retrieved, making it distinct from general site health or content listing tools.

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 offers almost no usage guidance regarding when to prefer this tool over others or in what scenario it is most appropriate. The phrase 'runs straight away' describes performance but not contextual usage.

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