Summarize a space

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds almost nothing beyond that — 'Reads community data' is vague and arguably inconsistent with a space-scoped tool; it says nothing about generation cost/latency, caching, or freshness of the AI summary.

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?

Two short, front-loaded sentences with no bloat, which is good, but the second sentence ('Reads community data') carries little information and borders on filler rather than earning its place.

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 and four parameters, the description should explain what the summary returns and how it relates to the space/message filters (e.g., date_from scoping). Instead it omits return-value expectations and the AI-generation nature entirely, leaving the agent under-informed for a non-trivial 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%, so all four parameters (account, space_id, date_from, first_unread_message_id) are already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 states a clear verb+resource ('Summarize a space'), but it is essentially a verbatim restatement of the title and does not distinguish this tool from neighbors like get_space or get_post_summary. It never clarifies that these are AI-generated summaries or what a 'space summary' comprises, so an agent cannot tell it apart from a generic retrieval call.

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?

There is no guidance on when to use this tool versus list_spaces/get_space/get_post_summary, and no mention of prerequisites or when summaries are unavailable. The only hint of context is the vague 'Reads community data.'

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