getTaggedEntities

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

No annotations are provided, so the description must disclose behaviors. It only states the read operation and a specific error condition. It does not describe pagination behavior (despite cursor and limit parameters), sorting, filtering effects, or any side effects. Minimal transparency.

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 sentences with no redundancy. The purpose is front-loaded, and the Enterprise constraint is stated immediately. Every sentence adds value.

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 5 parameters, no output schema, and no annotations, the description is insufficient. It fails to explain that results are paginated, what entity types are included, or how to use cursor for pagination. Sibling tools suggest entity-specific retrievers, yet this tool's cross-entity nature is not clarified.

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 has 100% description coverage, so the schema already documents each parameter. The description adds no additional meaning or context for parameters like slug, cursor, direction, entityType, or limit. Baseline score of 3 is appropriate.

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 clearly states the verb 'Gets' and the resource 'Postman entities by tag'. It also mentions the Enterprise-only limitation, which differentiates it from other get tools. However, 'Postman entities' is somewhat vague, lacking specificity about which entity types are returned.

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?

The description indicates when NOT to use the tool (non-Enterprise plans) due to 404 error. It does not provide guidance on when to use this tool versus sibling tools like getCollection or getSpec, which return specific entity types. Implied usage but lacks explicit alternatives.

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