tenki_get_workspace_settings

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive. The description adds valuable behavioral context by listing exactly what fields are returned and clarifying that idle timeout and max duration are not included here (set per sandbox). This goes beyond the annotations without contradicting them.

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 paragraph that front-loads the core purpose, then lists specifics. It is efficient and free of fluff, though a bulleted list could improve readability. The trailing clarification about per-session defaults is concise and useful.

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 read-only tool with no output schema, the description lists all returned fields and explains scope. It does not mention error cases or authentication, but given the simple input and read-only annotations, it provides sufficient context for an agent to call 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 schema describes workspace_id fully ('Workspace to read. Omit to use the API key's first workspace.'). The description adds no additional parameter information, so it relies entirely on the schema. With 100% coverage, a baseline of 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 begins with a clear verb ('Read') and specific resource ('a workspace's sandbox quotas and retention policy'), then enumerates exact fields. This unambiguously distinguishes it from related tools like tenki_get_workspace_usage or tenki_update_workspace_settings.

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 clear context: it is for workspace-level limits and explicitly notes there are no per-session defaults, which implies it is not for retrieving per-session settings. However, it does not name specific alternative tools or give explicit when-to-use conditions.

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