database.info

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

No annotations are provided, so the description carries full burden. It states 'Get', implying a read operation, but does not disclose what the status entails, whether it is safe, what permissions are needed, or what the response looks like. The behavioral transparency is minimal.

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 sentence, which is concise and front-loaded. However, it is too brief to be useful; it sacrifices critical detail for brevity. While not verbose, it does not earn its place by providing enough information to guide the agent.

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 no output schema, no annotations, and a single under-described parameter, the description is incomplete. It does not clarify what 'status' includes, the return format, or how session_id relates to other tools. The agent likely needs additional context to use this tool 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 schema has a single required parameter 'session_id' with no description (0% coverage). The tool description does not explain what session_id is, how to obtain it, or its format. The description adds no meaning beyond the schema, failing to compensate for the missing parameter documentation.

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 'Get database status for session' clearly specifies a verb and resource with a scope. It distinguishes from sibling database tools like database.snapshots or database.read_global by focusing on 'status' rather than snapshots or global data. However, it does not explicitly differentiate from similar retrieval tools, leaving some ambiguity.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or when not to use it. Given the large number of sibling tools, the lack of usage direction is a significant gap.

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