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

No annotations are provided, so the description must disclose behavioral traits. It does not mention that this is a read operation, any side effects, permissions, or response behavior. The phrase 'Access and manage' even misleadingly implies a broader scope than a getter.

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 a single generic sentence that provides no specific information. It is under-specified rather than appropriately concise, as no part of the text earns its place by helping the agent select or invoke the tool.

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?

With no output schema, the description must compensate by explaining purpose and behavior. Instead it gives a broad catalog API overview, omitting what a descriptor is, what the return value contains, and any usage context. This is completely inadequate for a tool with three parameters.

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 input schema already describes all parameters (100% schema coverage), including tagOrId and yaml. The description adds no additional parameter context, so it meets the baseline for schema-covered parameters but does not enhance semantics.

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 is a generic umbrella statement ('Cortex Catalog API - Access and manage your service catalog, teams, domains, and resources') and does not mention 'entity descriptor' or a retrieval action. It fails to state what this specific tool does, making it vague and indistinguishable from a broad platform description.

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?

There is no guidance on when to use this tool versus its siblings like getEntityDetails or listEntityDescriptors. No context or alternative mention is provided, leaving the agent without decision criteria.

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