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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds nothing beyond that — no note on cost, latency, or what a 'map' contains — so it earns no extra credit above the annotation baseline.

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?

A single short sentence with no padding, so it is front-loaded and economical. But its brevity reflects under-specification rather than effective conciseness given the tool's five parameters.

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 five-parameter tool with four required fields (including unexplained meta-parameters like reason and user_intent) and a real output schema, this one-liner leaves too much unresolved: what a map is, how window/subject affect it, and when it beats siblings.

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 60% and the description mentions only 'namespace', not the four required parameters (reason, user_intent, subject) nor the 'window' enum values. It fails to compensate for the undocumented parameters, especially 'subject', which has no schema description at all.

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?

States a verb ('Get') and a resource ('a Flowlines analysis map') and scopes it to 'one namespace', which helps distinguish it from list_maps and get_map_segment. However, 'Flowlines analysis map' is unexplained jargon, so an agent cannot fully tell what the returned artifact actually is.

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 indication of when to call this versus siblings such as list_maps, get_map_segment, or get_user_population_map, and no prerequisites stated. The only guidance is the implicit single-namespace scope.

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