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

With no annotations provided, the description carries full burden and excels: discloses READ-ONLY nature, idempotency, side effect of inserting into D1 usage_log, required APS scopes, rate limits, and detailed error codes with recovery actions. This goes far beyond a typical tool description.

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 structured into clear labeled sections (purpose, when to use, when not, scopes, rate limits, errors, side effects). Every sentence provides actionable information; no fluff. It is front-loaded with the core purpose and immediately usable guidance.

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 annotations and no output schema, the description covers all essential context: use cases, exclusions, scopes, rate limits, errors, side effects, and output fields. The error handling and recovery suggestions are particularly valuable. This is a complete standalone reference for an AI agent.

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 accepts zero parameters, and the input schema confirms this with 100% coverage. The description adds context by listing the output fields and the flattened-across-hubs behavior, but since there are no parameters, the baseline of 4 applies. No additional parameter semantics are needed.

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 uses a specific verb ('List') and clearly defines the resource ('every ACC/BIM 360 project') and output fields (hub_id, hub_name, etc.). It distinguishes itself from sibling tools by stating it is the tool to use when you need a project_id for other ACC tools, and explicitly notes the N+1 API calls behavior that differentiates it from alternatives.

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 explicit 'When to use' and 'When NOT to use' sections, citing specific sibling tools for both scenarios. It also warns about performance implications ('N+1 API calls... avoid calling it in tight loops'), giving clear alternative guidance.

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