deployment_count

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

No annotations provided and description fails to disclose return type format (integer/object?), idempotency, or error conditions. The 'filter criteria' claim without schema parameters creates behavioral uncertainty.

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?

Optimal two-sentence structure with zero waste. Front-loaded action verb and efficient cross-reference to sibling tool avoids redundant filter documentation.

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?

Critical gaps remain: no return value specification (scalar vs object), no resolution of the filter/schema mismatch, and no safety annotations. For a computational endpoint without output schema, the description fails to specify what constitutes a successful response.

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?

With zero parameters in schema (baseline 4), the description attempts to add value by referencing deployment_list for filter definitions. However, the empty schema contradicts this guidance, creating implementation confusion despite the semantic intent.

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?

Clearly states the tool counts deployments using specific verb and resource. The mention of 'filter criteria' distinguishes it from retrieval operations, though this creates confusion given the empty input schema showing no parameters.

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?

References deployment_list to indicate filter parity, implicitly suggesting use when only cardinality is needed versus full listing. Lacks explicit guidance on when to prefer count over list, or prerequisites for use.

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