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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering safety. Description adds bulk execution behavior via ids, but doesn't disclose return format or error behavior. No contradiction.

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?

Two short sentences with no fluff; front-loads the core purpose then adds bulk detail.

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 simple read-only get operation with two flat string/array parameters and no output schema, the description plus annotations provide sufficient context. Bulk support is the only extra behavior, and it is mentioned. Could specify response details but 'details' implies that.

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?

Schema has 0% description coverage. Description clarifies that 'ids' enables bulk execution, adding meaning to the optional parameter, but doesn't elaborate on 'id' or value formats beyond schema's type constraints.

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?

Description uses specific verb 'Gets' with resource 'details for a Supabase project', clearly differentiating from siblings like supabase_list_projects (list all) and supabase_get_project_url (specific URL). Bulk support note adds precision.

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 alternatives or exclusions, but the bulk support sentence implies usage for single or batched project detail retrieval. It doesn't state when to prefer this over list_projects or get_project_url, leaving usage context implied.

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