plainweave_entity_intent_context_get

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

No annotations provided, so the description carries full burden. It discloses a read operation and hints at unavailability, but lacks details about data freshness, authorization requirements, or side effects.

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 sentence, efficiently front-loaded with the main action. However, the second part 'unavailable state' is confusing and could be clarified, making it less concise in meaning.

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 one unexplained parameter, no annotations, and a cryptic description, the tool lacks sufficient detail for correct invocation. The output schema might help but is not described or provided.

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 only parameter 'entity_refs' has no description in the schema (0% coverage). The tool description does not explain what entity_refs are or how to format them, leaving the agent without guidance.

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 'Read local entity intent context' which is a specific verb and resource. It distinguishes from siblings by specifying 'local' and mentioning 'unavailable state', implying it is a fallback when live resolution is unavailable.

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 implicitly suggests use when 'Live Loomweave resolution is unavailable state', but does not explicitly state when to use this tool versus alternatives, nor provides exclusions or prerequisites.

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