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

Annotations already indicate read-only behavior, and the description adds transparency by stating that bearer links, file bodies, and credentials are not returned. This gives a clear picture of side-effect-free behavior.

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 a single, focused sentence with no redundant or extraneous content, making it easy to parse and apply.

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?

It covers the main return values and explicitly lists what is not returned, but it omits potential error conditions, permission requirements, and output schema details, so completeness is moderate.

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?

project_id and room_id are somewhat self-explanatory, but the schema provides no parameter descriptions and the tool description does not explain their exact meaning, constraints, or relationship, leaving room for ambiguity.

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?

Clearly states that it reads specific SparkRoom data (name, audience controls, document metadata, review fingerprint) and identifies the use case ('before adding monthly reports'). This distinguishes it from write or mutation tools.

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?

Provides a specific use case, but does not explicitly contrast with sibling tools like sparkroom.get or founder_close.refresh_room, so an agent may need extra inference to choose among similar read operations.

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