Show a space

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so safety is covered. The only added phrase, "Reads community data," is vague and adds no behavioral detail such as authentication, error behavior when the ID is missing, or scope of data returned. Minimal value beyond annotations.

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 sentences, front-loaded with the operation, with no wasted words. It is efficient, though the brevity comes at the cost of substance rather than being elegantly dense.

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?

For a simple read tool with fully documented parameters and no output schema, the description is minimally sufficient. However, it never states what the response contains or the identity of the "account"-scoped context, leaving the agent to rely entirely on schema and annotations.

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 account and space_id are already documented in the schema (account even notes it selects credentials, not a remote community ID). The description adds nothing beyond this, so the baseline of 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?

"Show a space" restates the title with a verb+resource, so the basic operation is discernible, but it does not explain what a space is, what is returned, or how it differs from siblings like get_space_group, list_spaces, or get_space_member. "Reads community data" is vague filler that adds no real specificity.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as list_spaces (to find a space) or get_space_group/get_space_member for adjacent resources. The agent must infer the role of this tool from the name alone.

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