plan_cross_entity_read

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

No annotations provided; description only says 'plan' without disclosing side effects, authentication needs, rate limits, or what the plan output entails.

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?

Single sentence is concise but lacks informative details; front-loads the action but under-specifies.

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 4 parameters and no descriptions, no annotations, and an output schema not elaborated, the description fails to provide sufficient context for an AI agent to correctly invoke the tool.

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?

Description provides no explanation of the four parameters (root_entity, goal, root_id, needs) despite 0% schema description coverage. Terms like 'properties' and 'includeReferencedEntities' are not mapped to parameters.

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 states the tool plans an efficient read using properties and includeReferencedEntities, which is clear but does not explicitly distinguish it from sibling tools like execute_read_plan or validate_read_plan.

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?

No guidance on when to use this tool versus alternatives; no mention of prerequisites, exclusions, or context.

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