Get Space By ID

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, and the description goes beyond them by disclosing the authentication requirement (TweetAPI API key), the request volume (one request per call), and the cost profile (~1 unit, with a per-result cost estimate). These are exactly the operational facts an agent needs before calling a metered external endpoint.

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?

Three short sentences with the core purpose front-loaded, followed by cost/auth context and no redundant restatement of the title. Every clause carries information an agent can act on.

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 single-parameter read tool with an output schema (so return values need no explanation), the description covers purpose, input forms, auth, cost, and the dependency on the streaming sibling. Nothing an agent needs in order to call it correctly is missing.

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% and the spaceId property already documents both accepted formats, including the full Space link example. The description restates "space ID or Space link" but adds no format, normalization, or error-handling detail beyond the schema, 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?

States a specific verb and resource ("Fetch details for a Space by its space ID or Space link") and adds a distinguishing payload detail: it returns the media key needed by tweetapi_space_stream_url. That lets an agent separate it from the sibling stream-URL tool without opening either schema.

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?

Implies a usage sequence by noting the returned media key is needed for tweetapi_space_stream_url, which is a concrete when-to-use signal. It does not explicitly state when-not to use it or name any other alternative among the ~50 siblings, so it falls short of a 5.

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