enable_hosted_storage

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

The description discloses key behaviors: recording explicit consent, returning a disclosure of stored data and erasure instructions, and requiring authentication. While no annotations are provided, it covers essential aspects without contradiction. A slightly higher score would require mention of reversibility or impact on existing storage.

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 concise (three sentences) and front-loaded with the main action. Every sentence adds value, with no redundancy or wasted words.

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 the tool's simplicity (no parameters, output schema exists), the description provides sufficient context: it explains the effect, the consent recording, disclosure, and prerequisites. It could be improved by briefly mentioning what the output schema contains, but the description's statement about returning disclosure is adequate.

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 tool has zero parameters and 100% schema coverage, so the baseline is 4. The description adds meaning by explaining what the tool accomplishes without needing parameters, such as provisioning a database and recording consent.

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 clearly states the tool's purpose: enabling NeuroDock-hosted storage by provisioning a private database and recording consent. It distinguishes itself from the sibling tool 'connect_byos_storage' by specifying the alternative for maximum privacy.

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 explicitly states when to use this tool (to enable hosted storage) and provides an alternative ('connect_byos_storage') for different privacy needs. It also notes the prerequisite of a signed-in NeuroDock account.

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