get_entity_schema

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

With no annotations, the description carries the burden of disclosing behavior. It details the return structure (properties and relationships) and implies a read-only operation via 'Get.' It does not discuss permissions or error scenarios, but for a read-only schema tool this is adequate.

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 concise, front-loaded with the primary purpose, and uses a bulleted 'Returns' section to clearly list output fields without unnecessary prose. Every sentence contributes to understanding.

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 single-parameter schema retrieval tool with no output schema, the description fully explains the return values and the tool's purpose. It covers both the properties and relationships aspects, making it self-contained and complete.

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 description coverage is 100% (the 'entityName' parameter already includes an example and clarification). The description adds no extra parameter-specific detail, so the baseline of 3 applies.

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 starts with a specific verb and resource: 'Get the full schema of an entity.' It clearly distinguishes itself from siblings like get_entity_record (which gets data) and list_entities (which lists names) by focusing on properties and relationships.

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 clear usage context: 'Use this to understand what data an entity holds and how it connects to other entities.' It does not explicitly name alternative tools or exclusion conditions, but the context is unambiguous for a schema query.

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