get_community_space

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

The description adds the HTTP method and confirms read-only behavior, complementing annotations like readOnlyHint and idempotentHint. It does not contradict annotations and provides sufficient context for safe invocation.

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 concise (four lines) with front-loaded key information (READ-ONLY, HTTP method). Every sentence adds value without redundancy.

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 single parameter and lack of output schema, the description fully covers the tool's purpose and behavior. It tells the agent what to expect and how to use it 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?

The only parameter 'id' is already fully described in the input schema with a clear description. The description does not add additional semantics beyond what the schema provides, so baseline 3 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?

The description clearly states it retrieves a specific community space by ID, using the verb 'Get' and specifying the resource. It distinguishes from sibling tools like create_community_space or delete_community_space.

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 indicates it is a read-only GET operation, but it does not explicitly mention when to use it over alternatives like get_community_spaces for listing all spaces. However, it is clear that it retrieves a single space by ID.

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