Get Entity Card

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

Without annotations, the description discloses the behavior: it returns the entity record, open tasks, recent interactions, and linked transactions. It does not detail side effects, permissions, or recency timeframe, but the overall behavior is transparent enough for an agent.

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 efficiently convey the tool's purpose and value. No extraneous words; every sentence earns its place.

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 no output schema, the description adequately explains what the tool returns and its overarching benefit. It could marginally benefit from mentioning output format or limitations (e.g., recency of interactions), but it is largely complete for agent decision-making.

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 coverage is 100% with both parameters fully described. The description adds no additional meaning beyond the schema, meeting the baseline expectation but not exceeding it.

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 tool gets a complete picture of an entity including its record, open tasks, recent interactions, and linked transactions. It specifies the verb and resource, and explicitly distinguishes from multiple separate calls, answering 'what's going on with X?'.

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 advises using this tool to replace multiple separate calls for a consolidated view, implying it should be used when a comprehensive snapshot is needed. While it does not list explicit when-not-to-use scenarios, the guidance is clear and contextually strong.

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