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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lowered. The description adds value by clarifying that filters are 'exact-match' and that the query is for 'one entity', which informs expected behavior (no fuzzy search, scoped to a single entity type). This is contextual detail beyond the annotations, though it does not describe pagination or return format.

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, efficient sentence that front-loads the verb and resource. There is no filler or repetition. Every part earns its place by conveying action, scope, and a key behavior (exact-match) in minimal words.

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 the tool has 6 parameters (2 required) and no output schema, the description provides the core purpose but omits details like the return structure (probably a list of records) and how filters interact with nesting (filters is an object). The schema covers parameter types, but without an output schema the agent might benefit from a note on the response. The description is adequate for a simple query tool but not fully 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%, so all six parameters have their own descriptions in the schema. The tool description mentions 'exact-match filters' which echoes the filters parameter's schema description but does not add new semantics. With full coverage, the baseline is 3, and the description does not exceed that.

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 action (Query), the resource (app data records for one entity), and the optional capability (exact-match filters). It is specific enough to distinguish from mutation siblings like create_entity_records or delete_entity_records, and from get_entities which likely lists entities rather than records. It is not a tautology and uses a precise verb.

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 implies when to use this tool (to query records of a single entity) but does not explicitly state when not to use it or mention alternatives. For instance, it does not say 'use get_entities to list entities' or 'use update_entity_records to modify'. An agent must infer the appropriate sibling based on context, so guidance is adequate but not explicit.

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