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

Annotations already declare readOnly, idempotent, and non-destructive, and the description redundantly restates these. It earns credit for adding behavior not in the annotations: 'does not advance unread' and the REST endpoint GET /v1/maturity, plus a note that the tool does not record a yes.

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?

Six short, front-loaded sentences with the core purpose first and constraints after. Slightly telegraphic, but every line carries information and nothing is padded.

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 no output schema, describing what comes back (maturity level plus yes tally, and the meaning of yes_count/needed/you_yes) is exactly right. The 'next step' phrase is left vague, which is the only real gap.

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 tool takes zero parameters, so the baseline is 4. The description uses the space to explain the response fields (yes_count, needed, you_yes) rather than parameters, which 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?

States a specific verb and resource ('Read this Space's maturity') and clarifies the domain vocabulary with '(line / log / articles)'. It implicitly separates itself from the maturity_yes sibling via 'Does not record a yes', but never names that sibling, so it falls short of a 5.

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 line 'Does not record a yes' hints that a separate tool handles recording, and 'Read-only: does not advance unread' gives a side-effect constraint, but no explicit when-to-use or named alternative is provided. An agent must infer that maturity_yes is the counterpart.

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