get_space_usage

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

No annotations provided, so description carries full burden. Fails to disclose what 'usage' entails (used vs total vs available bytes), whether shared folders are counted, response format, or caching behavior. 'Current' implies real-time but doesn't confirm freshness guarantees.

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?

Single 7-word sentence with no redundancy. Appropriate length for a parameterless getter tool; every word earns its place by identifying action, scope, and target resource.

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?

Adequate for a zero-parameter tool, though no output schema exists to document return values. Description successfully identifies the entity being retrieved but omits details about what specific metrics are returned (bytes, percentages, limits).

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?

Zero parameters exist with 100% schema coverage (trivially empty schema). Baseline 4 applies as there are no parameters requiring semantic elaboration beyond the empty schema definition.

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?

Specific verb 'Get' and clear resource 'Dropbox account space usage' provided. Distinguished from file-operation siblings (copy, delete, list_folder, etc.) by specifying account-level metadata rather than file content operations.

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?

No explicit when-to-use guidance or alternatives mentioned. Usage is implied by the specific functionality (retrieve space usage), but lacks guidance on when to prefer this over calculating sizes via list_folder or prerequisites like authentication scope.

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